l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
January 6: Social gathering
Next Installfest:
TBD
Latest News:
Nov. 18: Club officer elections
Page last updated:
2005 Mar 14 09:48

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox] News from Vancouver: Debian to cut to 4 major arches for Etch(and Sarge news...)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox] News from Vancouver: Debian to cut to 4 major arches for Etch(and Sarge news...)



This is buzz right now on #debian IRC channels.

As of etch (next release after sarge), Debian will split itself to
"major" and "SCC" (second-class citizen) arches.  Major arches are i386,
powerpc, ia64, and amd64.

    http://lists.debian.org/debian-devel-announce/2005/03/msg00012.html

    To: debian-devel-announce@lists.debian.org
    Subject: Bits (Nybbles?) from the Vancouver release team meeting
    From: Steve Langasek <vorlon@debian.org>
    Date: Sun, 13 Mar 2005 20:45:09 -0800

    The release team and the ftpmasters are mutually agreed that it is
    not sustainable to continue making coordinated releases for as many
    architectures as sarge currently contains, let alone for as many new
    proposed architectures as are waiting in the wings.  The reality is
    that keeping eleven architectures in a releasable state has been a
    major source of work for the release team, the d-i team, and the
    kernel team over the past year; not to mention the time spent by the
    DSA/buildd admins and the security team.  It's also not clear how
    much benefit there is from doing stable releases for all of these
    architectures, because they aren't necessarily useful to the
    communities surrounding those ports.

    <...>

    We project that applying these rules for etch will reduce the set of
    candidate architectures from 11 to approximately 4 (i386, powerpc,
    ia64 and amd64 -- which will be added after sarge's release when
    mirror space is freed up by moving the other architectures to
    scc.debian.org).  This will drastically reduce the architecture
    coordination required in testing, giving us a more limber release
    process and (it is hoped) a much shorter release cycle on the order
    of 12-18 months.

    Architectures that are no longer being considered for stable
    releases are not going to be left out in the cold.  The SCC
    infrastructure is intended as a long-term option for these other
    architectures, and the ftpmasters also intend to provide porter
    teams with the option of releasing periodic (or not-so-periodic)
    per-architecture snapshots of unstable.


Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    After all, if you can't trust a Romanian tabloid, then who can you trust?
    - The Register

Attachment: signature.asc
Description: Digital signature

_______________________________________________
vox mailing list
vox@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox


LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.