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

[Jesse Keating]

On Wed, 2009-12-02 at 15:26 -0800, J.H. wrote:
> 
> 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. 

Let me explain the base problem a bit more.

"rawhide" as it stands today (or well during F12 development and
earlier) was schizophrenic.

Just after the release of Fedora 11, rawhide was a free-for-all, rapid
change, high liklihood of being broken, development crashlanding zone.
This continued on until we hit feature freeze, and then suddenly the
changes stopped, and we switched gears in that repo to polish up the
features for the Alpha release.  Then it unfroze and a flood of pent up
builds landed and had some people doing polish work, and some people
doing wild-ass development.  Then near Beta it froze again and no
changes happened whilst we polished for Beta.  We remained frozen and
only changes that were deemed safe enough for the release went out until
finally we had our GOLD package set, and then the flood of pent up
builds were let lose, and rawhide once again was the wild wild west of
crazy-ass changes.

So you see, rawhide was /already/ a moving target, and outside observers
had no real good idea what state rawhide was in, and whether or not it
was safe to consume.

What we're moving to is more inline with what Debian has.  Rawhide is
our "unstable".  Then pending release which we branch away from rawhide
(and are trying to figure out where to land) is our "testing", where as
the finished releases like 12, 11, 10 are our "stable".  We're taking
the moving target that was rawhide and making it a constant entity, and
moving the freeze/polish effort that was making it a moving target into
its own path.

Just thought of another alternative path,

pub/fedora/linux/pending/<arch>

to go along with

pub/fedora/linux/development/<arch>

Of course, pending/ would only have content after we've branched away
from rawhide, but that's a minor detail.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://mail.ale.org/pipermail/mirror-admin/attachments/20091202/0498d496/attachment-0001.bin 
-------------- next part --------------
--