[arch-dev-public] freezing core/extra - cleanup testing
jason at archlinux.org
Wed Mar 12 14:47:48 EDT 2008
In general I'm not understanding your email. Let me ask for clarification.
On Wed, Mar 12, 2008 at 01:14:49PM +0100, Pierre Schmitz wrote:
> Hi everybody,
> to avoid any chaos in our repos we should think about freezing core and extra.
> I would propose that we set a date till when we should fix the outstanding
> bugs in core packages.
You want to set a date where we'll stop updating core? You say it's to
avoid chaos, what does this mean?
> Afaik there are only some problem with the new initscripts (e.g. hwclock
> problem) and I am unsure about netcfg. Shouldn't this be merged with
> initscripts? There seems to be some redundant code atm.
Now you're talking about a specific set of package changes that seem
unrelated to what you were saying above...
> After that we should be able to create a first release candidate of the new
> iso. Then we shhould concentrate on testing those isos.
Ok, so... merge initscripts, fix outstanding core bugs by a certain date
then make isos and test them.
> In parallel we have new libtool, gcc and friends in testing. So I would
> recommend that we only use testing for building packages and keep core/extra
Wait... and keep testing the way it is? So the new isos should work with
the old versions of libtool, gcc, etc? Does this mean we'll have problems
when we push libtool, gcc, etc out of testing?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the arch-dev-public