#1813 NORM Update.: Reset build numbers to 50000.
Zarro Boogs per Child
bugtracker at laptop.org
Sun Nov 4 00:23:12 EDT 2007
#1813: Reset build numbers to 50000.
----------------------------------+-----------------------------------------
Reporter: cjb | Owner: cscott
Type: defect | Status: new
Priority: normal | Milestone: Update.2
Component: ofw - open firmware | Version:
Resolution: | Keywords:
Verified: 0 |
----------------------------------+-----------------------------------------
Comment(by cscott):
My opinion is that we should *not* reset the build numbering. My counter
proposal:
Our official build numbering will be continuous, with un-prefixed versions
being 'release candidates' of one form or another.
Official builds will go in:
http://download.laptop.org/os/official
These will be signed with MP, etc, keys.
Unofficial, unsigned, release candidates are in:
http://download.laptop.org/os/candidate
I don't expect there to be many (if any) of these; the only reason would
be if we wanted to test a candidate with known-bad security properties.
Development builds have prefixes. 'joyride-3', 'kernel-625', etc. They
will not be signed.
They are in:
http://download.laptop.org/os/development
Free development between major releases, occurs on joyride. When a
release freezes, we form a 'killjoy' fork and synchronize build numbers.
If the last official release was 625, then we start with 'killjoy-626'.
Near the end of the release process, when we're satisfied that security-
critical bugs (at least) have been stomped out, the killjoy prefix is
stripped out and we start making official release candidates (629,630,...)
which are all signed.
So, simple rule: prefix == unsigned. No prefix == signed.
Old 'official' releases that were not signed (prior to 623ish) go in:
http://download.laptop.org/os/historic
--
Ticket URL: <http://dev.laptop.org/ticket/1813#comment:7>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list