No Frozen Rawhide coming soon! New paths on mirrors!

Mike Chambers mike at miketc.net
Mon Feb 8 22:33:54 UTC 2010


On Mon, 2010-02-08 at 09:07 -0800, Jesse Keating wrote:


> /pub/fedora/linux/development/13/  will become the new path of the
> branched Fedora 13 content.  This is where builds from the F-13/ branch
> in CVS will go, after they pass through bodhi as "stable".

So let's take above directory layout.  So if I normally mirror rawhide,
is the above dir what I would want to change to, to follow f13 devel and
where the normal everyday package updates (stable ones I mean suspect?)
would happen that are geared for F13? So this dir will also contain the
night builds (isos?) as well as the boot.iso/whateverelse images from
the /images dir are created here nightly and can be installed from like
rawhide used to be during each cycle?
> 
> /pub/fedora/linux/updates/testing/13/  will be where potential Fedora 13
> builds go after passing through bodhi as "testing".  This is where
> you'll find the latest stuff proposed for freeze break and where testing
> and peer review of these freeze breaks will happen.  When a maintainer
> feels enough testing has happened, or enough karma triggers the bodhi
> auto request, the build will be marked "stable" and show up in the
> development/13 tree at the next nightly compose.

So the above dir, would be used like official releases are done, via
package updates go to testing first, then when feel stable (or however
long it goes), they move to the devel/13 dir in the 1st paragraph?  And
test images are created here as well?

Guess shall try to summarize what is happening to make sure
understanding what is happening...


1 - Rawhide dir is same, cept at feature freeze it moves on to the next
future fedora version.

2 - Devel Feature Freeze branch (at feature freeze), that stable
packages/builds are built each day, for the current version being worked
on?  And also a testing devel feature freeze branch for testing
packages/builds for problems before they hit stable?

3 - Official release branch, currently as is for the officially released
versions, to include stable and testing updates.

If above is correct or at least if not worded right but I am
understanding at least, then have a question or two, but not to argue,
but to understand why or the underlying part to it.  

Why couldn't rawhide just be the stable part and just add a testing dir
to it?  

Do the maintainers multitask that much to work on updates for official
releases, develop a new release, and start work on the next release?
>From just a user/tester perspective, seems a bit much and too many paths
to follow and keep up with.  But hey, if you devel guys/maintainers are
all bout it, whom I to judge? haha.

Anyway, just asking and clarifying (guess you can call this *follow up*)
what is going on, in laymen terms? LOL

(hrm, think I just confused the hell outta myself and maybe others)

-- 
Mike Chambers
Madisonville, KY

"Best lil town on Earth!"



More information about the devel mailing list