Several developers were on today’s design forum and discussed the pros & cons of options for the impending platform release:
- Release Platform 2.2 from master (including all bug fixes, but omitting any new features or complicated bug fixes)
- Sorting through all commits in master since the 2.1.x branch and properly leaving out any new features or complicated bug fixes was felt to be much work to get done and get a release out in 2017.
- Release Platform 2.2 using Core 2.1.1
- Since we want to keep Core & Platform versions synchronized, releasing Platform 2.2 would require a new 2.2.x branch that would basically be 2.1.x with few if any changes, so not worth the effort.
- Release Platform 2.1.2 using Core 2.1.1 + updated modules
- More feasible to get done in 2017, but would miss out on bug fixes in master.
- Release Platform 2.1.2 using Core 2.1.1 along with a few key bug fixes from master + updated modules
- Our best option. Leveraging Core 2.1.1 allows us to fast-track the release, but we could still take the opportunity to select a handful of key bug fixes in master that have not yet been backported to be included.
So, the consensus, in order to try to get a release out before the year ends, was to leverage have a Platform 2.1.2 release that uses Core 2.1.1 along with a handful of key bugfixes from master + updated modules. @wyclif should be posting about this soon, asking folks to nominate any straightforward bug fixes (that have been fixed in master but not yet backported) to be included in the release.