This past week, we reached another milestone on WPSiteSync for Content. The Release Candidate was published in the WordPress.org repo. So far, the feedback has been incredible. We are jazzed seeing everyone so excited!
At ServerPress, one of our goals has always been transparency with the public. So, we thought we’d take this opportunity to share our software development journey with fellow developers who happened to be our loyal customers!
So, what is the difference between a Release Candidate and General Release?
A Release Candidate is a beta version that’s ready to be a final product, unless significant bugs emerge. At this point, the product is pretty stable; all product features have been tested through several beta cycles by multiple testers with no more “showstopper” bugs.
A General Release is a stabilized version ready for mass market adoption. Not only has it gone through several rounds of testing, it has had the time to be exposed to most user scenarios and fringe case bugs that simply could not have been identified without vast market feedback.
How does this apply to WPSiteSync for Content?
Normally at this point of the development cycle, a General Release can be announced. We have been very fortunate in receiving the public’s assistance in bug reporting. We are confident in the stability of WPSiteSync for Content. However, given the nature of WPSiteSync, which could affect live data on websites, we took the incremental development approach and decided to publish a Release Candidate instead of announcing a General Release this past week. This ensures a solid foundation with greater quality control.
Currently, the data is being transferred properly from staging and live environment consistently. This process has been validated through numerous rounds of testing with various user cases. In this respect, we feel good in categorizing WPSiteSync for Content as a General Release.
Because the product gained traction pretty quickly, WPSiteSync simply has not had enough time on the market to be exposed to all the user cases internationally. There may be minor feature glitches we find as we continue expanding our testing arena. Because of this, we made the final decision on publishing the Release Candidate instead of announcing a General Release.
We are committed to producing a rock solid product.
Just this past week, we noticed an issue with a hosting provider. A particular hosting provider had disabled a built-in PHP function that we were relying on. Without this, we were unable to communicate between the two sites. We had to come up with a work around in order to get the Content and the Featured Images syncing correctly to the live site. No data was lost so it’s not a show-stopper. But hosting provider issues were unexpected in the development of WPSiteSync. We learned something new!
So, is WPSiteSync Release Candidate reliable?
Overall, we are very pleased with the performance of WPSiteSync for Content. The general consensus is in agreement. But we still need your assistance in providing more feedback! We want to know what’s not working for you, especially if you feel your development environment is out of the ordinary. The only way we can write bullet-proof code is to learn edge cases.