Regular monthly small dot point releases
The AU team slates a release at the end of every month to get all the smaller pieces of work out and available for instances. This release is usually a 1.n.n, as to date they have been smaller releases and not worthy of a 1.n.
Schedule for these releases:
Apr 28 - 1.8.9
May 26 - 1.8.11
Jun 30 - 1.8.12
Jul 28 - 1.8.13
Aug 25 - 1.8.14
September 27 - 1.9
October 20 - 1.10 (pending)
December 15 (or the Wednesday after)
Note: if a team requires a small change or bug fix for their instance then this can be accommodated outside of these end of month planned releases.
Larger feature releases
When larger features are delivered as part of a project (e.g. Spree Upgrade, Multilingual) we will schedule a stand-alone 1.n release.
Estimated schedule for project work in the pipeline:
1.9 - Spree Upgrade (step 6)
1.x - Subscriptions
[ORIGINAL POST TO KICK OFF DISCUSSION ]
Was chatting with the AU team about how we manage releases for the year. Last year we started out with a plan to have a release at the end of every month…which we did fairly consistently until we got to the point where we didn’t have anything major to release and started putting out ad-hoc dot point releases (e.g. 1.8.8 which was released this week).
We were thinking, now that there is a lot of activity happening and more and more code being merged into master by non-AU team people that it was worth revisiting this idea and scheduling some kind of release on the last friday of every month.
Random thoughts about this:
Everyone in the community will know to expect a release at the end of every month.
Those putting issues through the pipeline will know if they want something in a release that it has to be ready by the Wednesday before release day. Including being reviewed and merged to master.
The AU team can then better manage their end of the pipeline and not be up till the wee hours of the morning trying to get the big queue of things waiting to be merged reviewed and pushed to master on the day of the release (@oeoeaio I’m looking at you ) .
We can decide on the day whether there is enough to release and whether it deserves a full dot point release (e.g. 1.9) or is a smaller release (e.g. 1.8.9).
We don’t have to only put out releases on this day, we can also do it at other points when there is a need (e.g. a severe bug is found or a feature release is ready mid-month).
Thoughts? If everyone is ok with this then the next release will be March 31 (possibly 1.8.9 but also possibly 1.9 if Standing Orders beta functionality is ready to go as planned).