From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How about a monthly bumpday?
Date: Wed, 10 Mar 2010 10:11:31 -0800 [thread overview]
Message-ID: <b41005391003101011u48f101fcj8567bb8e8f3b0ec8@mail.gmail.com> (raw)
In-Reply-To: <20100310144159.GV30005@halcy0n.com>
On Wed, Mar 10, 2010 at 6:41 AM, Mark Loeser <halcy0n@gentoo.org> wrote:
> Mike Frysinger <vapier@gentoo.org> said:
>> On Tuesday 09 March 2010 23:08:24 Sebastian Pipping wrote:
>> > 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?
>>
>> for the maintainer-needed ones, np. for the ones with maintainers, i think
>> you need an ack from someone first.
>
> I don't even think the maintainer-needed ones should be bumped. Who
> knows what bugs you are introducing into the tree. This is why things
> eventually get treecleaned.
>
> As Mike said, for ones with maintainers, don't touch them unless you
> have explicit permission. We have maintainers for a reason, and if you
> don't know the intricacies of the package, you shouldn't be touching it.
> You should know how it works, how to test it, and what the normal
> problems of a bump are.
>
> With that being said, I don't really see the point of a bumpday. These
> day ideas are ignoring the fact that we don't have enough active developers,
> which is the real problem.
>
We have plenty of developers, the problem is we have too many packages ;p
-A
> --
> Mark Loeser
> email - halcy0n AT gentoo DOT org
> email - mark AT halcy0n DOT com
> web - http://www.halcy0n.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFLl6+3CRZPokWLroQRAp07AKDgqdRi1gWsIp0wG+QLIaYEXss5OwCdHNZ6
> Owj8ESEixDWVN03OwJV53EQ=
> =F2pI
> -----END PGP SIGNATURE-----
>
>
next prev parent reply other threads:[~2010-03-10 18:11 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
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 [this message]
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=b41005391003101011u48f101fcj8567bb8e8f3b0ec8@mail.gmail.com \
--to=antarus@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