From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] 2006.0 planning
Date: Mon, 05 Dec 2005 14:37:12 -0500 [thread overview]
Message-ID: <1133811432.10256.6.camel@cgianelloni.nuvox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Do we need to have a 2006.0 planning meeting or can we do all of it
on-list? Basically, I just need to know who is planning on releasing
for 2006.0 and what they plan on releasing. I would also need to know
school/work/vacation schedules for the first quarter of next year, so we
can plan accordingly. I'll start off with myself.
I know that I will be attending FOSDEM at the end of February and will
probably be in Europe for at least 2 weeks after. I will also be in
Boston for Linux World on April 3rd-6th. This would make the month of
March a pretty bad time for me to do the release, depending on how much
work I can offload onto the new x86 Release Coordinator, thunder.
I already sent out the information on what x86 will be releasing to the
list, so I am not going to repeat that here.
--
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 --]
next reply other threads:[~2005-12-05 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 19:37 Chris Gianelloni [this message]
2005-12-06 15:54 ` [gentoo-releng] 2006.0 planning Lars Weiler
2005-12-06 19:48 ` Chris Gianelloni
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=1133811432.10256.6.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