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 06:17:33 +0100	[thread overview]
Message-ID: <4B972B6D.2020602@gentoo.org> (raw)
In-Reply-To: <20100309210004.51b15a4e@angelstorm>

On 03/10/10 06:00, Joshua Saddler wrote:
> I'm prolly not the only one who feels this way, so you really need to pick your bugs carefully!

Agreed, yes.


> Bumpdays are otherwise a good idea, though I'm not sure why we need a separate day for that in addition to our standard bugdays.

While bugday is also meant to activate developers it's primarily focused
on users fixing bugs, making them able to do that and doing proxy commits.

I guess a developer doing the bump himself is much faster than waiting
for and working with a user on that.  It would help to teach users but
it would work against the goal of getting all the bump requests closed.

Also, another day means one more day a month with people working on
Gentoo theoretically.



Sebastian



  reply	other threads:[~2010-03-10  5:18 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 [this message]
2010-03-10 13:59       ` Ben de Groot
2010-03-10 18:50         ` Sebastian Pipping
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=4B972B6D.2020602@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