public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] 2006.0 planning
Date: Tue, 06 Dec 2005 14:48:42 -0500	[thread overview]
Message-ID: <1133898522.17235.15.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20051206155445.GA13268@elladan.wh-og.hs-niederrhein.de>

[-- Attachment #1: Type: text/plain, Size: 2743 bytes --]

On Tue, 2005-12-06 at 16:54 +0100, Lars Weiler wrote:
> * Chris Gianelloni <wolf31o2@gentoo.org> [05/12/05 14:37 -0500]:
> > I would also need to know school/work/vacation schedules
> > for the first quarter of next year, so we can plan
> > accordingly.
> 
> First quarter is okay with me, as I guess I'm not in the
> end-phase of my diploma by then.  I may have two or three
> exams in January/February, but that should not hold back for
> releasing.
> 
> As I won't manage Gentoo at Fosdem in 2006, I will attend as
> a visitor only.  And as I live in Europe, I don't need a two
> week vacation after it ;-)  The question is, should we
> release before Fosdem (end of February) or after it (end of
> March when Chris returned)?

If we release before FOSDEM, it means we pretty much need to get started
now to make sure our tools are well tested and stabilized before we make
our portage snapshot freeze.  I would really prefer we not have to
update genkernel/catalyst versions after the snapshot.  That seems to
always cause friction.  What this means is we would need all of you to
test catalyst 2.0_rc* now and report back any problems as soon as
possible.

> > I already sent out the information on what x86 will be releasing to the
> > list, so I am not going to repeat that here.
> 
> I'll try to make the ppc-release as similar to x86 as
> possible, regarding the installed applications on the
> InstallCD and USE-Flags.
> 
> Open questions:
> - nptl with -nptlonly and it's open bug

I'll leave this up to you.  I *really* don't want anyone using nptlonly,
but if it causes problems on your architecture not to, well, that is
completely your prerogative as the Arch Coordinator.  I'm not going to
try to make you do something broken, but if there's any way to get "nptl
-nptlonly" working, then I would say to go for that.

> - further merge of ppc with ppc64
> - XLiveCD with installer

I'm pretty sure that the Installer won't be ready for PPC.  I can give
you my spec files and fsscripts/etc along with an gli ebuild set if you
would like to build an Installer CD now for testing, but this one might
be a ways off.  That being said, I'd love to get more information from
you on how to setup X auto-detection stuff on PPC for a LiveCD.  I am
attempting now to normalize this and make it more useful and more
universal across architectures, so any information would be greatly
appreciated.

> - support of 43p-RS/6000
> - further OldWorld-support
> - alpha-support for AirportExtreme

I'm guessing this is all kernel-related stuff, so I leave that to you.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-06 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 19:37 [gentoo-releng] 2006.0 planning Chris Gianelloni
2005-12-06 15:54 ` Lars Weiler
2005-12-06 19:48   ` Chris Gianelloni [this message]
2005-12-06 19:35 ` Bryan Østergaard
2005-12-06 20:01   ` Chris Gianelloni
2005-12-06 20:48     ` Bryan Østergaard
2005-12-06 20:59       ` Chris Gianelloni
2005-12-06 20:56 ` Jeffrey Forman
2005-12-11  7:25 ` Kumba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1133898522.17235.15.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox