Today we are shining a light on a information that the community has long requested: our release calendar for the next versions of PrestaShop 1.7 and 1.6!
In short: we intend to release 4 minor versions of PrestaShop 1.7 in 2017, and monthly patch versions of both 1.7 and 1.6.
When, you ask? Here’s a handy table:
Now, for the longer part of the article…
The current release cycle
Keen readers of the Build devblog are aware that the last few releases have been dedicated to fixing issues and stabilizing both major versions of PrestaShop:
- PrestaShop 220.127.116.11 was released on November 7th, 2016, and has since received 4 patch versions – with the 5th coming very soon!
- PrestaShop 1.6 is in maintenance mode, and 5 patch versions have been released since September – with 18.104.22.168 coming soon too!
Hence, we’ve been roughly having 1 patch release per month for each supported version of PrestaShop. Because those releases are light, they make for easy upgrades, and thus safer merchants.
Regularity is key: we want our community to know that they can expect monthly improvements to their chosen version – with the exceptional additional patch release in case of a blocking issue or a security fix, of course.
Our plan for 2017
As written above, we’ve been releasing patch releases for both supported version of PrestaShop roughly every month. We plan on keeping that release schedule for patch versions: one each month for both 1.7 and 1.6.
As for when to expect minor releases (22.214.171.124, 126.96.36.199, etc.), here’s how we are planning to work things out:
- We want to have regular minor releases for 1.7.
- The Core team has been following the Scrum “Sprint” methodology for several months now, with each sprint lasting two weeks. If you don’t know what Scrum or a sprint are, read up! :)
- Our experience shows that it takes roughly 20 weeks from building the backlog to delivering QA results.
It takes two sprints to build the work backlog for a minor release, roughly six sprints to have those tasks developed and tested, and we are planning on two sprints after code freeze in order to have a proper QA process. One final sprint is dedicated to the release itself (packaging, final checks, Addons updates, etc.).
Count it up: that's 10 sprints from building the backlog to the end of QA.
Take your TI-81 out: that’s 20 weeks to have a minor version of PrestaShop, from planning to general release.
Thanks to parallel work (backlog for 188.8.131.52 being prepared while 184.108.40.206 is being coded and 220.127.116.11 is going through QA), we think we can have a minor release of v1.7 every 6 sprints – which means one release every 12 weeks, and therefore 4 minor releases of 1.7 in 2017.
Now you see where we stand. With these metrics, we were able to establish a release calendar for the whole year to come. While we cannot give precise release dates yet, the table that opens this article shows you our intents.
A few notes:
- All these dates are estimates. There are not set in stone, and may change depending on ongoing developments.
- There can be more than 2 patch releases for each 1.7 minor release. Indeed, should a pressing issue arise (such as an urgent issue or a security fix), we would of course build another patch version, released as soon as the fix is in place.
- While there is no mention of a possible v18.104.22.168, keep in mind that we are still open to a minor 1.6 version, should excellent (and 1.7-ported) community features justify it.
All of this we can call an industrialization of our releases. Release often, fix issues as soon as possible, and bring new features on a regular basis.
The Core and Product team comprises more than 20 people dedicated to improving both 1.7 and 1.6, with 1.6 having its own dedicated team. We are constantly improving our processes in order to have a faster reaction to community tickets or pull requests.
In the end, our aim is to keep on improving the codebase, making it stronger and more stable, while adding much-requested features all year long.
What’s it gonna be?
So, two new minor versions before summer, and 2 other by year’s end, great!
We have a pretty clear idea of what we want them to be. Here is a bird’s eye view:
- Should be released in March 2017.
- Main projects:
- General stability and feature improvement.
- 1.6-to-1.7 upgrader.
- Improved translation scope.
- Should be released in June 2017.
- Main projects:
- Reworked Advanced Stock Management feature.
- More to come!
- Should be released in September 2017.
- Main projects to be determined.
- Should be released in December 2017.
- Main projects to be determined.
Do you want to help on a specific topic? Let us know!
Given a version number MAJOR.MINOR.PATCH, increment the:Because of our own history, we chose to follow a SemVer-like versioning: 1.MAJOR.MINOR.PATCH. This means that, as of today (with 22.214.171.124):
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
- The next patch version is 126.96.36.199
- The next minor version is 188.8.131.52
- The next major version would be 184.108.40.206
There you go! The table will be updated as we go.
Tell us what you think!