Hi Holly, and thanks for your clear explanation, > > Hi list, i would like to have clarification regarding the policy of > > switching packages from testing to stable. Is this policy due to > > particular bugs in the packages? > > > No. Gentoo's "stable" and "testing" refers to the /ebuilds/, not the > packages.
Well, that was my fault in explaining..... i was referring to "versions" of a particular package.... > I'm not a dev, but from my experience, if upstream (the developers of a > particular package) release the package, then it is considered to be > 'stable' (insofar as it's releaseable, and Gentoo does not include betas > or development versions in the Portage tree). > > However, the ebuild script that allows the package to compile on Gentoo > may contain errors, so it must be tested. That is what ~ARCH is about; > making sure the provided ebuild compiles the source of the application > correctly and successfully with relationship to the rest of a Gentoo system. > > ~ARCH packages/ebuilds are normally tested for (30? 90?) days, after > which time if no bugs are filed, they generally move into stable. It is > hoped that users who use ~ARCH are willing to file or comment on bugs on > bugs.gentoo.org (b.g.o). The system only works if everybody helps. > At the root of my question there was the need to understand why kde 3.5.1 packages are still testing even if there aren't critical bugs at bugs.gentoo.org (as far as i was able to find...). However, many thanks, Regards, MC -- gentoo-user@gentoo.org mailing list
