public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How about a monthly bumpday?
Date: Wed, 10 Mar 2010 19:50:52 +0100	[thread overview]
Message-ID: <4B97EA0C.2010300@gentoo.org> (raw)
In-Reply-To: <e117dbb91003100559h2d5d32acve067db8c88c9208e@mail.gmail.com>

On 03/10/10 14:59, Ben de Groot wrote:
> I think it would be better to have it all happen on the same day. If those
> are easy bumps, they fit very well with bugday. And those devs who
> want to work on that, can then join the general bugday mayhem. ;-)
> You might be spreading things too thinly otherwise. And even for the
> more involved bumps it could be handy to have users around for
> testing.

Testing is a point, easy bumps are a point to.
The thing is bugday will soon not be thin anymore: it will require all
the attention of all online devs: there weill be no time to do bumps
that need your brain in parallel.  To summarize: we have to allow Gentoo
to grow or it won't.



Sebastian




  reply	other threads:[~2010-03-10 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  4:08 [gentoo-dev] How about a monthly bumpday? Sebastian Pipping
2010-03-10  4:32 ` Nathan Zachary
2010-03-10  5:00   ` Joshua Saddler
2010-03-10  5:17     ` Sebastian Pipping
2010-03-10 13:59       ` Ben de Groot
2010-03-10 18:50         ` Sebastian Pipping [this message]
2010-03-10 22:34           ` Ben de Groot
2010-03-10 17:23   ` Gilles Dartiguelongue
2010-03-10 12:35 ` Mike Frysinger
2010-03-10 14:41   ` Mark Loeser
2010-03-10 15:02     ` Markos Chandras
2010-03-10 17:43     ` Sebastian Pipping
2010-03-10 18:11     ` Alec Warner
2010-03-11  5:58     ` [gentoo-dev] " Ryan Hill
2010-03-19 12:36 ` [gentoo-dev] " Peter Volkov
2010-03-21  0:58   ` Sebastian Pipping

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=4B97EA0C.2010300@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@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