Levi Ramsey wrote:
On Thu, 6 Mar 2003, Andi Payn wrote:
A compromise might be to do a QA'd sub-release of Cooker every two months,
rather than every six months. A single team can work on a project with
release dates this short, spending a couple of weeks in freeze every two
months. I think most Cooker users would put up with these freezes in exchange
for an even-more-usable Cooker. And, more importantly, both Mandrake's team
and the user community would have more experience getting together a solid
release; it would require less work to tie together two months' worth of
development than six; and there'd be a solid way to back-track any subset of
the distro, if necessary, without going all the way back to the last major
release.
I would say that it should be made monthly, without formally freezing
Cooker per se (ie a fork 10 days before). As release time approaches, the
target final version would be based on which one of those snapshots seemed
to be the most stable (and thus on squashing as many bugs as possible in
that snapshot).
Levi Ramsey
[EMAIL PROTECTED]
If people are prepared to do this, then why not use a per-package flag
in line with the regime I mentioned earlier? The snapshot could be
packages which are stable (ie, 'green light'). If something people want
misses out because there's some problems with it, then people might push
to get it ready for the next snapshot, just one month away. And in that
time it could be relegated to orange light as people test and debug it.
Salut!
Paul
