Thursday: builds are uploaded on mirrors. Wednesday: builds are uploaded on the early pre-release site they are announced on the devel and qa mailing lists.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.Monday: commit deadline reminder is sent to devel, l10n mailing list before it happens.There are needed several actions for each build. The release consists of several beta and release candidate builds. The release can be delayed by few days because of blocker bugs, build problems, and other technical issues. It is because we are always a bit flexible. The release is time-based but the schedule defines calendar weeks instead of exact dates. See also the detailed schedule and the release notes.ħ.3 release Basic dates for the initial and bugfix releasesħ.2 release Basic dates for the initial and bugfix releasesħ.1 release Basic dates for the initial and bugfix releasesħ.0 release Basic dates for the initial and bugfix releasesĦ.4 release Basic dates for the initial and bugfix releasesĦ.3 release Basic dates for the initial and bugfix releases Still 7.4 release Basic dates for the initial and bugfix releases The simplified graphic below shows three releases placed on a timeline consisting of 24 months. Such problem would shift the final release by one week or even more. An extra RC might be needed if the final release candidate does not fit the Release Criteria. Note that the dates mentioned in the schedule might get shifted if there are serious technical or other problems with the release. More conservative users are advised to wait for a later X.Y.Z bugfix release. The first X.Y.0 release is intended for early adopters. In addition, they get many pure bugfix micro releases. As a result, users get new major version every six months with a wide range of features, fixes, and enhancements. 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.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. It is also the case that we will necessarily release earlier, and then rapidly, incrementally bug fix releases based on the previous stable version. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |