Current and future releases
- All release plans can be found on the Dirigible project overview page
As the development cycle gets closer to the release date, there is a general process we follow to ensure a successful and stable release.
When development reaches the final thirty days before release, two important steps begin the wind-down:
- The IP log is submitted. Before the logs are submitted, all outstanding dependencies must be checked and a decision made if they will appear in the upcoming release.
- A release review must be scheduled. This is done from the project page under a specific release.
During the last thirty days, development follows a different schedule. To make sure we do not introduce any regressions right before the release, we do the following:
- Keep working as usual for the first week of the wind-down. Typically no new features will be added at this time unless approved by the project lead.
- Once the release review is complete (typically by the second week of the wind-down), development changes to the "last chance" stage to put in changes (with no new features), with each change requiring a +1 from one other committer. This continues for the next two weeks.
- The last week is reserved strictly for testing and making critical fixes, with any fix requiring a +1 from two committers (ideally one of the committers being the project lead).
- After the release has been announced on the mailing list and dirigible.io, new and noteworthy blog posts are created.