--- Mike Nordell <[EMAIL PROTECTED]> wrote: > Paul Rohr wrote: > > Discovering bad bugs at step 3 is a clear > indicator that the release was > > *not*, in fact, ready for prime time. > > Indeed. Would it be feasible to create a "test" > release before major > releases? It would obviously be a greater burden for > all, and it would > probably create "test2" and so on releases, but it > would probably iron out > the "obvious" bugs.
Shouldn't we just be creating a branch/fork directly after the tag? New stuff would go into the new branch/ fork, keeping the original branch/fork nice and clean for when we find the big showstopper bugs. Andrew Dunbar. > Since I really don't know how much effort goes into > a full release-cycle > it's possible this idea is in reality not possible. > > /Mike - please don't cc > ===== http://linguaphile.sourceforge.net http://www.abisource.com __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
