[mirror-admin] No frozen rawhide and new mirror path

[J.H.]

Jesse Keating wrote:
> For Fedora 13 we are attempting something new, a new chapter in the
> development of Fedora. [1]
> 
> We are transitioning "rawhide" from the mixed bag of development,
> freeze, pending release, mass change, etc.. into a never freezing ever
> moving repository of developmental packages.  Rawhide the path won't
> ever freeze and won't ever be used for polishing a release.
> 
> We plan to branch Fedora 13 development away from rawhide at our Feature
> Freeze (scheduled for February 9th), into a new path on the mirror
> system, and use that path to freeze/polish/stage the Fedora 13 release.
> At the same time, the rawhide path would continue on and be the start of
> the Fedora 14 release development.
> 
> What does this means to mirrors?  It means a new path will be created,
> that will change nightly as polish continues.  This new path location
> has yet to be decided which is why I'm bringing this up to you.
> 
> We've had few suggestions, in no particular order:
>   pub/fedora/linux/releases/13/Everything
>   pub/fedora/linux/releases/test/13/Everything
>   (some new path as of yet un-imagined)
> 
> We've also heard some cons on these paths.
> 
> If we put stuff in releases/13/Everything, we will then have bits
> changing nightly in the releases/ tree which some mirrors may not be
> expecting.  The same goes with releases/test/13 however that could be
> mitigated by excluding the test/ path)
> 
> If we put stuff in releases/test/13 it would cause confusion when
> combined with releases/test/13-Alpha and releases/test/13-Beta as they
> are released.
> 
> Obviously no cons on the un-imagined paths (:
> 
> So I ask you, the mirrors we are ever so grateful for, what is your
> opinion on this matter?  Where would you like to see a "second rawhide"
> appear?
> 

Honestly if your going to have a constantly moving target like that, and 
fundamentally change the way that 'rawhide' works that's probably "bad".

We've already got fedora-enchilada as a module, why not add another 
directory under that for the ever moving, ever changing entity 
(rawhide-nonstop?) and leave the traditional 'rawhide' as the place 
where the final spit and polish occurs as suggested?  This also means 
that there is no early attempts by people thinking that because of the 
freeze that things are ready for general consumption in terms of 
alpha/beta testing till those actually come out in the traditional 
paths.  Also makes it easy that mirrors won't really have to change 
existing excludes or includes unless they have fedora-enchilada and 
don't want the constantly churning tree.

Dunno, just my thoughts.  I have no real complaints about the above 
proposed paths, just kinda thinking out loud so to speak.

- John 'Warthog9' Hawley

--