Time-based release trains have been shown to produce the best quality Free software. A time based release is one that does not wait for either features, or bug fixes - but is based (as purely as possible) on time. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. It is also the case that we will necessarily release earlier, and then rapidly, incrementally bug fix releases based on the previous stable version. Thus if you have a need for the very highest quality version, it can make sense to defer a move until the first or perhaps second minor point release.
- LibreOffice does bi-annual, predictable releases that are in sync with other Free Software projects (eg. Gnome) and are at least one month ahead major Linux distribution releases.
- Synchronizing time-based release schedule with the wider Free Software ecosystem also has huge advantages, by getting our new features, out to users as quickly as possible – with a minimum of distribution cycle lag. In consequence, we aim at six monthly releases, and over time nudge them to align well with the March/September norms.
- Time-based release trains have been shown to produce the best quality Free software. A time based release is one that does not wait for either features, or bug fixes - but is based (as purely as possible) on time. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. It is also the case that we will necessarily release earlier, and then rapidly, incrementally bug fix releases based on the previous stable version. Thus if you have a need for the very highest quality version, it can make sense to defer a move until the first or perhaps second minor point release.
- There are 2 branches: Fresh (the newest release) and Still (the previous release), which are intended for mainstream feature users and conservative, corporate deployments respectively.
- As a result, users get new major version every six months with a wide range of features, fixes, and enhancements. In addition, they get many pure bugfix micro releases. The first X.Y.0 release is intended for early adopters. More conservative users are advised to wait for a later X.Y.Z bugfix release.
Note that the dates mentioned in the schedule might get shifted if there are serious technical or other problems with the release. An extra RC might be needed if the final release candidate does not fit the Release Criteria. Such problem would shift the final release by one week or even more. Template:LibOReleaseLifecycle/ar
|7.0.0 (freeze: week 29)||Week 19 , أيار ٤, ٢٠٢٠ - أيار ١٠, ٢٠٢٠||Week 32 , آب ٣, ٢٠٢٠ - آب ٩, ٢٠٢٠|
|7.0.1||Week 33 , آب ١٠, ٢٠٢٠ - آب ١٦, ٢٠٢٠||Week 36 , آب ٣١, ٢٠٢٠ - أيلول ٦, ٢٠٢٠|
|7.0.2||Week 38 , أيلول ١٤, ٢٠٢٠ - أيلول ٢٠, ٢٠٢٠||Week 41 , تشرين الأول ٥, ٢٠٢٠ - تشرين الأول ١١, ٢٠٢٠|
|7.0.3||Week 43 , تشرين الأول ١٩, ٢٠٢٠ - تشرين الأول ٢٥, ٢٠٢٠||Week 46 , تشرين الثاني ٩, ٢٠٢٠ - تشرين الثاني ١٥, ٢٠٢٠|
|7.0.4||Week 48 , تشرين الثاني ٢٣, ٢٠٢٠ - تشرين الثاني ٢٩, ٢٠٢٠||Week 51 , كانون الأول ١٤, ٢٠٢٠ - كانون الأول ٢٠, ٢٠٢٠|
|7.0.5||Week 06 , شباط ٨, ٢٠٢١ - شباط ١٤, ٢٠٢١||Week 09 , آذار ١, ٢٠٢١ - آذار ٧, ٢٠٢١|
|7.0.6||Week 15 , نيسان ١٢, ٢٠٢١ - نيسان ١٨, ٢٠٢١||Week 18 , أيار ٣, ٢٠٢١ - أيار ٩, ٢٠٢١|
|End of Life||May 31, 2021|
|6.4.0 (freeze: week 02)||Week 42 , تشرين الأول ١٤, ٢٠١٩ - تشرين الأول ٢٠, ٢٠١٩||Week 05 , كانون الثاني ٢٧, ٢٠٢٠ - شباط ٢, ٢٠٢٠|
|6.4.1||Week 06 , شباط ٣, ٢٠٢٠ - شباط ٩, ٢٠٢٠||Week 09 , شباط ٢٤, ٢٠٢٠ - آذار ١, ٢٠٢٠|
|6.4.2||Week 09 , شباط ٢٤, ٢٠٢٠ - آذار ١, ٢٠٢٠||Week 12 , آذار ١٦, ٢٠٢٠ - آذار ٢٢, ٢٠٢٠|
|6.4.3||Week 13 , آذار ٢٣, ٢٠٢٠ - آذار ٢٩, ٢٠٢٠||Week 16 , نيسان ١٣, ٢٠٢٠ - نيسان ١٩, ٢٠٢٠|
|6.4.4||Week 18 , نيسان ٢٧, ٢٠٢٠ - أيار ٣, ٢٠٢٠||Week 21 , أيار ١٨, ٢٠٢٠ - أيار ٢٤, ٢٠٢٠|
|6.4.5||Week 24 , حزيران ٨, ٢٠٢٠ - حزيران ١٤, ٢٠٢٠||Week 27 , حزيران ٢٩, ٢٠٢٠ - تموز ٥, ٢٠٢٠|
|6.4.6||Week 30 , تموز ٢٠, ٢٠٢٠ - تموز ٢٦, ٢٠٢٠||Week 33 , آب ١٠, ٢٠٢٠ - آب ١٦, ٢٠٢٠|
|6.4.7||Week 39 , أيلول ٢١, ٢٠٢٠ - أيلول ٢٧, ٢٠٢٠||Week 42 , تشرين الأول ١٢, ٢٠٢٠ - تشرين الأول ١٨, ٢٠٢٠|
|End of Life||November 30, 2020|
|6.3.0 (freeze: week 29)||Week 19 , أيار ٦, ٢٠١٩ - أيار ١٢, ٢٠١٩||Week 32 , آب ٥, ٢٠١٩ - آب ١١, ٢٠١٩|
|6.3.1||Week 32 , آب ٥, ٢٠١٩ - آب ١١, ٢٠١٩||Week 35 , آب ٢٦, ٢٠١٩ - أيلول ١, ٢٠١٩|
|6.3.2||Week 36 , أيلول ٢, ٢٠١٩ - أيلول ٨, ٢٠١٩||Week 39 , أيلول ٢٣, ٢٠١٩ - أيلول ٢٩, ٢٠١٩|
|6.3.3||Week 41 , تشرين الأول ٧, ٢٠١٩ - تشرين الأول ١٣, ٢٠١٩||Week 44 , تشرين الأول ٢٨, ٢٠١٩ - تشرين الثاني ٣, ٢٠١٩|
|6.3.4||Week 47 , تشرين الثاني ١٨, ٢٠١٩ - تشرين الثاني ٢٤, ٢٠١٩||Week 50 , كانون الأول ٩, ٢٠١٩ - كانون الأول ١٥, ٢٠١٩|
|6.3.5||Week 05 , كانون الثاني ٢٧, ٢٠٢٠ - شباط ٢, ٢٠٢٠||Week 08 , شباط ١٧, ٢٠٢٠ - شباط ٢٣, ٢٠٢٠|
|6.3.6||Week 15 , نيسان ٦, ٢٠٢٠ - نيسان ١٢, ٢٠٢٠||Week 18 , نيسان ٢٧, ٢٠٢٠ - أيار ٣, ٢٠٢٠|
|End of Life||May 29, 2020|
The release is time-based but the schedule defines calendar weeks instead of exact dates. It is because we are always a bit flexible. The release can be delayed by few days because of blocker bugs, build problems, and other technical issues.
The release consists of several beta and release candidate builds. There are needed several actions for each build. The ideal workflow looks like:
- Monday: commit deadline; reminder is sent to devel, l10n mailing list before it happens
- Tuesday: the tag is created on a commit that builds and passes unit-, subsequent-, and smoke-tests; tag is announced on the devel and qa mailing lists
- Wednesday: builds are uploaded on the early pre-release site; they are announced on the devel and qa mailing lists
- Thursday: builds are uploaded on mirrors. They are announced via many channels, e.g. mailing lists, twitter
- Friday: builds are available via the official pre-release site
The final release is usually announced on Thursday, few days after the final release candidate is out.
Note that we are very strict about commits to the final release candidate, so full regression test is not needed. It is used as the final build when it passes the needed tests. It is just renamed on mirrors.
The schedule is based on the following rules:
- do the major release every six months and synchronize it (at least one month ahead) with major Linux distributions; it always comes with a wide range of features, fixes, and enhancements
- do a pure bugfix release every month after the main release until it is good enough even for the most conservative people; do it less frequently afterwards
- do pure bugfix releases, including security fixes, until the next release is ready for most conservative people
- do not do two builds the same week.
The result is the following template:
|x.y feature freeze||Jun(ب)||Dec(ب)|
|x.y.0 first release||Aug(ب)||Feb(ب)|
|x.y.1 bugfix release||Sep(ب)||Mar(ب)|
|x.y.2 bugfix release||Oct(ب)||Apr(ب)|
|x.y.3 bugfix release||Nov(ب)||May(ب)|
|x.y.4 bugfix release||Dec(ب)||Jun(ب)|
|x.y.5 bugfix release||Feb(م)||Aug(م)|
|x.y.6 bugfix release||Apr(م)||Oct(م)|
حيث (ب) يعني بداية الشهر، (م) يعني منتصف الشهر و (ه) يعني نهاية الشهر.
The release plans for the first version of each major release indicate a "hard English string & UI freeze". The idea is to make the lives of translators easier. The translators should be able to trust that no new translatable strings are added into the UI or Help files between the period of the string freeze and release.
After the first version of a major release is out, correcting mistakes in the UI and Help strings is fine. Any completely new content should target the next major release.
We do several builds around each release. The following versioning scheme is used:
- X.Y.0.0.alphaZ - Zth alpha version of the initial release
- X.Y.0.0.betaZ - Zth beta version of the initial release
- X.Y.0.Z - Zth release candidate of the initial release, last rc is considered as final and put on the main download page
- X.Y.1.Z - Zth release candidate of the 1st bugfix release, last rc is considered as final and put on the main download page
It seems to be the best compromise with the following advantages:
- easy to understand for normal users, alpha, beta flags are known from other projects, so they set reasonable expectations
- correct alphabetical sorting in RPM, Bugzilla
- “easy” to parse (alpha/beta strings delimited by dot)
There was a long discussion about this scheme on the mailing list.
Accelerating the release cycle
This acceleration of the release cycle involves some considerable release engineering and QA effort. To reduce the cost of these, we work to provide complete (ie. containing all languages) daily snapshots of the master branch to allow continual testing of code improvements. This works partially already, as can be seen/downloaded from here.
Similarly, we plan to increasingly automate the build process to allow a much lower-touch release flow, and to continue to shrink the footprint of our binaries to allow far more rapid transfer of product-equivalent builds.
A release normally has a lifetime of around nine months. We consider a release to have reached its End of Life (EOL) one month after the last planned release.
If you want longer term support for a release, you’re encouraged to engage any certified L3 provider who could provide you with the service.
Because of the amount of data, the releases were split out to ReleasePlan/Archive.