On Tue, Jan 20, 2004 at 11:42:56PM -0800, Ryan Finnie wrote: > I'm still trying to figure out the reasoning behind this. If the idea > is to not leave tickets open, what about the other 4758 open tickets? > I would consider the most logical procedure for testing to be: > 1. Version bump (or whatever reason), new version committed to cvs as > ~arch. > 2. User tests new version, opens a bug and reports success (or lack > thereof). > 3. More users test, commenting on original bug #. > 4. If enough people report success (or enough time goes by after > initial verification), ebuild is marked stable and bug is closed. > > I can't find any documentation of a process here, but this is what I > gather: > 1. Version bump (or whatever reason), new version committed to cvs as > ~arch. > 2. Somebody with cvs commit access stumbles on the ebuild sometime in > the future, checks bugzilla, sees no problems submitted, and marks > stable. It is documented: http://www.gentoo.org/doc/en/policy.xml under 'Moving package versions from ~ARCH to ARCH'
Quote When a package version has proved stable for sufficient time and the Gentoo maintainer of the package is confident that the upgrade will not break a regular Gentoo user's machine, then it can be moved from ~ARCH to ARCH. An indication of the package's stability would be no verified or unresolved bug report for a month after the version's introduction. For your case submitted that it works 1 day after the ebuild was placed into the tree, that is not nearly enough time for it to be thoroughly tested. Please also bear in mind that the developers keep some things in ~arch for other reasons than just stability or time, such as testing specific features. To re-iterate, it is not an 'OR' relation (as your item number 4) but rather an 'AND' relation. In tree sufficent time AND no problems reported. -- Robin Hugh Johnson E-Mail : [EMAIL PROTECTED] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgp00000.pgp
Description: PGP signature
