On Sun, 2006-03-19 at 07:56 -0700, Duncan wrote: > Matthias Langer posted <[EMAIL PROTECTED]>, > excerpted below, on Sun, 19 Mar 2006 15:24:19 +0100: > > > I'm just curious: What is the reason that firefox-1.5.x is still in > > ~arch ? > > General policy is that an ebuild should be bug-free in ~arch for 30 days > before it is stabilized. Individual herds and maintainers may have their > own policies, but the above 30 day guideline is the general Gentoo rule of > thumb. > > Looking at the changelog, mozilla-firefox-1.5.0.1-r2 was only added to the > tree on February 24. The -r2 indicates updates serious enough to bump the > release number were released at least twice, and the 1.5 ebuilds are at > -r9, indicating 10 versions (the first being -r0, not marked with an > release number, of course). > > That's a /lot/ of versions! I'd guess there have simply been enough > issues that no version of 1.5 has yet made it 30 days bug-free in ~arch, > altho the .0.1-r2 version above is getting close to 30 days in ~arch now, > tho I don't know its bug status. > > I often check the portage tree changelogs and Gentoo bugzilla site status > of particular packages that I'm interested in. I'm glad the info is > available, as it has proven useful quite often. > > -- Thanks for your answer; however, i've seen new versions of firefox getting from ~arch to stable much faster than 30 days, but i guess that was because of security issues; by the way, i was happy to read
" *mozilla-firefox-1.5.0.1-r1 (09 Feb 2006) 09 Feb 2006; <[EMAIL PROTECTED]> +mozilla-firefox-1.5.0.1-r1.ebuild: official branding support, ewarn about regchrome " that gentoo now has official branding support ... Matthias -- gentoo-dev@gentoo.org mailing list
