public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How about a monthly bumpday?
Date: Tue, 9 Mar 2010 21:00:04 -0800	[thread overview]
Message-ID: <20100309210004.51b15a4e@angelstorm> (raw)
In-Reply-To: <4B9720D6.6010702@gentoo.org>

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

On Tue, 09 Mar 2010 22:32:22 -0600
Nathan Zachary <nathanzachary@gentoo.org> wrote:

> On 09/03/10 22:08, Sebastian Pipping wrote:
> > Hello!
> >
> >
> > We have about 500 bump request open at the moment:
> > https://bugs.gentoo.org/buglist.cgi?quicksearch=bump
> >
> > I assume that quite a few of them would be no big deal to their
> > maintainers in Gentoo.
> >
> >
> > Bugday is occupying the first Saturday of the month: how about bumpday
> > on the third Saturday of the month?  First bumpday could be March 20th,
> > 10 days from now.
> >
> > What do you think?
> >
> >
> >
> > Sebastian
> >
> >   
> Not sure that my opinion matters all that much as I'm not currently
> doing ebuild work, but I think this idea could really help out the
> status of the tree.  Attached to it could be a stabilisation day as well.
> 
> --Nathan Zachary

The ones that I'm CCed on, either as proxy maintainer or because I have some other interest, I prolly would mind. They're not simple revbumps, but they have dependency changes and/or other complicated changes, which is the only reason why they're still open. My bugs can't be solved with a simple rename-and-commit.

I'm prolly not the only one who feels this way, so you really need to pick your bugs carefully! Otherwise we'll end up with another screwed-up mess like the one we just went through with patrick.

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-10  5:00 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 [this message]
2010-03-10  5:17     ` Sebastian Pipping
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=20100309210004.51b15a4e@angelstorm \
    --to=nightmorph@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