public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-releng] 2006.0 planning
@ 2005-12-05 19:37 Chris Gianelloni
  2005-12-06 15:54 ` Lars Weiler
                   ` (3 more replies)
  0 siblings, 4 replies; 9+ messages in thread
From: Chris Gianelloni @ 2005-12-05 19:37 UTC (permalink / raw
  To: gentoo-releng

[-- 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 --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2005-12-11  7:26 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox