<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
I'm not sure if Thunderbird actually sent the email, if it did sorry
for the extra message:<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
What about something along the lines of this:<br>
Moving current rawhide into its own directory within "development" (not
sure of the logistical nightmares that could potentially come up as a
result of that), and add your release branches within the "development"
folder as well.<br>
<br>
For example:<br>
Move current contents of pub/fedora/linux/development/ to
/pub/fedora/linux/development/<wbr>rawhide/<br>
Add pub/fedora/linux/development/<wbr>releases/<number>/Everything<br>
<br>
Then for the traditional alpha, beta, preview, etc... releases you can
still hardlink accordingly from
pub/fedora/linux/development/<wbr>releases/<number>/Everything<br>
<br>
This would address the concern of mirrors seeing unexpected bits in
releases because all changes are being kept within the development
directory.<br>
<br>
On 12/2/09 3:54 PM, Jesse Keating wrote:
<blockquote cite="mid:1259794450.12203.139.camel@localhost.localdomain"
type="cite">
<pre wrap="">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?
1: <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal">https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal</a>
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
--</pre>
</blockquote>
</body>
</html>