RFC: changing versioning of fedora-release in rawhide

[Jeremy Katz]

On Tue, 2007-11-20 at 15:01 -0500, Bill Nottingham wrote:
> Jeremy Katz (katzj at redhat.com) said: 
> > On Tue, 2007-11-20 at 14:50 -0500, Bill Nottingham wrote:
> > > Josh Boyer (jwboyer at gmail.com) said: 
> > > > > That requires going to another repo/web page/irc client/source of information
> > > > > to figure out and download whatever that version is.
> > > > 
> > > > You can use koji's downloadbuild (or whatever it's called) without too
> > > > much trouble.  This is rawhide after all.  Not for the faint of heart.
> > > 
> > > Right, but you still have to know *what the old version is*. And that
> > > would still work for my proposal - what I don't understand is why we'd
> > > be wedded to the current practice of shipping intentionally broken repo
> > > files.
> > 
> > I'd go an alternate route -- let's instead have the mirrorlists redirect
> > to rawhide for versions like 8.90, etc and get rid of the separate
> > development repository.  If you want to jump versions, change your
> > fedora-release.  This then gives us some nice consistency 
> 
> Then how do you switch to rawhide from a regular install?

>From the nice and unwritten page which links you to the current rawhide
fedora-release package.  

Realistically, you probably want the simple stupid plugin to allow you
to set the release version if you go this route.  But at the same time,
I don't think that the route of switching streams often is really a case
that you optimize for.

The current situation makes things a bit confusing to a user who *isn't*
interested in tracking development because they have out of the box the
following repo choices
  [ X ] Fedora
  [ X ] Fedora Updates
  [   ] Fedora Updates-Testing
  [   ] Fedora Development
not to mention source and debuginfo (which I'm tempted to just filter
from the UI, although it'd be nice if I didn't have to do so based on
just the repoid)

Jeremy