On Sun, 2005-09-04 at 14:40 -0600, Joshua Baergen wrote:
> A possible way to alleviate this is proactivity on the maintainer's
> part. Our current rule for going testing->stable is 30 days. If we
> could alert the arch teams x number of days in advance they could
> test
> it before the end of the period minimizing delays. Since all arch
> teams
> would need this alert a relevant script could be created/modified.
That's where having some devs/ATs running stable, and others running
testing really helps.. That and chroots for core packages going from
package.masked to testing. It's worked well for amd64 that way.
--
Homer Parker
Gentoo/AMD64 Arch Tester Strategic Lead
[EMAIL PROTECTED]
--
[email protected] mailing list
