In order to allow work to continue on the master branch while we move closer to a 0.10.0 release, I’ve created the following branches:
0.9.x-branch (maintenance branch) * Should be inactive unless important fixes are discovered. * Changes should be cherry-picked from master unless specific to 0.9.x 0.10.x-branch (security branch) * Active branch for 0.10.0 release. * Changes should be cherry-picked from master to be included in the release (e.g. STORM-714, STORM-617) 0.11.x-branch (Nimbus HA branch) * Should be up merged to master when master changes. I’m not very excited about having to keep 0.11.x in sync with master, but I think the Nimbus HA work needs as many eyes and as much testing as possible. Having a dedicated branch will make it easier to create preview releases and allow users to kick the tires. It will also ease some of the burden on Parth who’s spent a lot of time keeping that work upmerged. If anyone has any questions, concerns or suggestions regarding branch/release management, let me know. -Taylor
signature.asc
Description: Message signed with OpenPGP using GPGMail
