Fedora Core 1 Testing Update: gcc-3.3.2-6
Sean Estabrooks
seanlkml at rogers.com
Mon Jan 12 17:26:50 UTC 2004
On Mon, 12 Jan 2004 17:12:35 +0000
Tim Waugh <twaugh at redhat.com> wrote:
> On Mon, Jan 12, 2004 at 11:56:00AM -0500, Sean Estabrooks wrote:
>
> > Shouldn't the flow of an rpm be something like:
> >
> > development -> testing -> stable ?
>
> No. The 'development' packages are built in a rawhide build
> environment -- you certainly don't want those ending up as stable
> updates for Fedora Core 1.
>
> Basically a package is either built for testing (and then perhaps
> moved to stable) *or* for development.
Hey Tim,
Ok, i guess that makes some sense. My own feeling is that the
development branch should not be behind the testing branch of
the current release. All i was really asking was shouldn't it be
released to"rawhide" ie. development branch first or at least in
parallel? If it's good enough to be pre-stable, isn't it good enough
for the development branch?
This would increase the exposure and perhaps reveal additional issues,
prior to going stable. My other reason is admittedly somewhat selfish in
that i only have a local mirror of the development rpms and would dislike
having to mirror all the testing rpms just to get the odd rpm that appears
there first. This can't be good for the download sites either.
Cheers,
Sean
More information about the fedora-test-list
mailing list