I would like to understand the branch/version system you use. I've noticed you have a 5-5 stable branch (https://github.com/rhomobile/rhodes/tree/5-5-stable) but the modifications of the new released versions (listed here rhomobile.tau-technologies.com/list.html) doesn't seem to be on that branch. Also, the version file (https://github.com/rhomobile/rhodes/blob/master/version) still contains "5.5.0" while the last released version is 5.5.18 if I'm not mistaken.
Post by Konstantin Rybas on Mar 29, 2017 11:41:34 GMT
1. Rhodes versioning
1.1 developers versions - build from current developer(Master) branch X.X.N example: 5.5.6
1.2 major releases (deep tested versions) N.N example: 5.5, 6.0
1.3 stable releases (based on major version with critical fixes and important changes) X.X.0.N example 184.108.40.206
2. Development flow We push all fixes/new features to developer's Master branch and then prepare next actual developer version of Rho. Basically we provide commit links and dev version of Rho gems to our customers. Some customers merge commits into their gems manually, some of them use dev Rho gems to test fixes. Later we also provide stable release. Approximately we can provide stable release 1 time per 2 weeks.
3. Recommendations for customers: In case of make process faster and agile - we recommend to use actual developer version of Rho for testing bug fixes and new functionality on customer's side. But production releases of customer's apps we recommend to build against major Rhodes releases or stable releases.