Difference between revisions of "Release schedule"

Finnix, the LiveCD for system administrators
Jump to navigation Jump to search
(Created page with "== Release frequency == Twice per year, on the second Thursday of May and November. This schedule is not guaranteed, as factors can delay a release or cause an off-cycle rel...")
 
 
Line 1: Line 1:
 
== Release frequency ==
 
== Release frequency ==
  
Twice per year, on the second Thursday of May and November.  This schedule is not guaranteed, as factors can delay a release or cause an off-cycle release to be made.
+
TBD.
  
 
== Release schedule ==
 
== Release schedule ==
  
=== T-4 weeks: Kernel freeze ===
+
=== T-4 weeks ===
  
 +
==== Kernel freeze ====
 
A final kernel version is decided upon and built.  Focus shifts from development to testing.
 
A final kernel version is decided upon and built.  Focus shifts from development to testing.
  
=== T-2 weeks: RC freeze ===
+
=== T-2 weeks ===
  
 +
==== RC freeze ====
 
<tt>finnix-release</tt> package is updated and uploaded.  ISOs are produced from NEALE, and from this point, any build produced is considered a true release candidate.  If release-critical bugs are found, they are dealt with via individual package updates to the RC NEALE environment, rather than a new full NEALE build.  Testing matrix begins.
 
<tt>finnix-release</tt> package is updated and uploaded.  ISOs are produced from NEALE, and from this point, any build produced is considered a true release candidate.  If release-critical bugs are found, they are dealt with via individual package updates to the RC NEALE environment, rather than a new full NEALE build.  Testing matrix begins.
  
=== T-1 week: ISOs mastered ===
+
=== T-1 week ===
  
 +
==== ISOs mastered ====
 
Final ISOs are mastered, and a go/no-go is decided for release.
 
Final ISOs are mastered, and a go/no-go is decided for release.
  
=== T-4 days: ISOs uploaded ===
+
=== T-4 days ===
  
 +
==== ISOs uploaded ====
 
ISOs are uploaded to the master rsync server, to allow 24 hours for mirrors to sync.
 
ISOs are uploaded to the master rsync server, to allow 24 hours for mirrors to sync.
  
=== T-3 days: Torrent RSS updated ===
+
=== T-3 days ===
  
 +
==== Torrent RSS updated ====
 
The BitTorrent RSS feeds are updated to point to the new release.
 
The BitTorrent RSS feeds are updated to point to the new release.
 +
 +
=== T-1 day ===
 +
 +
==== Announcement prepared ====
 +
Release announcement draft prepared.
  
 
=== Release! ===
 
=== Release! ===
  
 
Announcements, etc, etc.
 
Announcements, etc, etc.
 +
 +
==== Launchpad updates ====
 +
Select "Create release" for the milestone.  Change "Fix committed" bugs to "Fix released" for any milestone bugs.  For any milestone bugs which are not "Fix committed", re-evaluate the bug.
  
 
[[Category:Development]]
 
[[Category:Development]]

Latest revision as of 05:32, 6 May 2013

Release frequency

TBD.

Release schedule

T-4 weeks

Kernel freeze

A final kernel version is decided upon and built. Focus shifts from development to testing.

T-2 weeks

RC freeze

finnix-release package is updated and uploaded. ISOs are produced from NEALE, and from this point, any build produced is considered a true release candidate. If release-critical bugs are found, they are dealt with via individual package updates to the RC NEALE environment, rather than a new full NEALE build. Testing matrix begins.

T-1 week

ISOs mastered

Final ISOs are mastered, and a go/no-go is decided for release.

T-4 days

ISOs uploaded

ISOs are uploaded to the master rsync server, to allow 24 hours for mirrors to sync.

T-3 days

Torrent RSS updated

The BitTorrent RSS feeds are updated to point to the new release.

T-1 day

Announcement prepared

Release announcement draft prepared.

Release!

Announcements, etc, etc.

Launchpad updates

Select "Create release" for the milestone. Change "Fix committed" bugs to "Fix released" for any milestone bugs. For any milestone bugs which are not "Fix committed", re-evaluate the bug.