On Sat, 26 Feb 2005 20:16:55 -0500, seth vidal wrote:
> >No, it doesn't. Sorry. It doesn't answer my earlier questions. It doesn't
> >answer when and whether to mass-rebuild.
>
>
> Well I think the answer, if you want to take my direction is this:
>
> 1. you get YOUR packages together.
> 2. we all encourage the other packagers to do the same for theirs
> 3. We set a bright deadline for devel tree release of extras and ask the
> packagers to stick to it.
> - I think maybe we should have that bright line be one week before the
> fc4t1 release - essentially slushy-freeze extras for 'devel' at the same
> time core freezes.
> 4. we figure out what's broken and fix it in that week, then release
> on-around the same time.
>
> 5. wash-rinse-repeat for fc4t2, t3 and final.
>
> Then we're ready to go!
My plan would have been this:
1. bump release of every package in "devel"
2. make sure that every update of FC-3 and older either loses
RPM version comparison compared with "devel" or is also imported
into "devel" tree with a higher release number
Then we would be ready for a mass-rebuild any time.
