[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Testing test releases: do not update (was: yum.conf that works)



On Sun, Feb 22, 2004 at 12:06:06PM -0500, William Hooper wrote:
> 
> Axel Thimm said:
> 
> > I would think the reason to have a test release is to have a well
> > defined point in development time to test against. If you point your
> > package resolvers to development/rawhide, then that's what you will be
> > testing instead.
> >
> > E.g. if you want to have FC2test1 installed and tested, file bug
> > reports etc., then do not update. Or if you do, probably you should
> > not file bugs against FC2test1 anymore (but FC devel), as the set of
> > bugs will already be different.
> 
> The point you are missing is that FC2test2 will just be another snapshot
> from FC devel.

Who would imagine that? ...

> If everyone is running FC2test1 and not updating then FC2test2 will
> come out basically untested.  This is not what we want.

Doesn't this reduce FCtest1 to an installer for rawhide with a test
for anaconda? Given the possibilities provided by modern package
resolvers like apt/yum you can jump on rawhide much easier than
sucking iso images to be outdated the next day.

> My experience from the Severn beta says that "test" releases are expected
> to be updated from Rawhide (devel) so that:
> 
> - Everyone doesn't keep reporting bugs that have been fixed
> - Everyone can test what will become Test2
-- 
Axel Thimm physik fu-berlin de

Attachment: pgp00102.pgp
Description: PGP signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]