From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How about a monthly bumpday?
Date: Sun, 21 Mar 2010 01:58:53 +0100 [thread overview]
Message-ID: <4BA56F4D.5090603@gentoo.org> (raw)
In-Reply-To: <1269002218.3855.53.camel@tablet>
On 03/19/10 13:36, Peter Volkov wrote:
> В Срд, 10/03/2010 в 05:08 +0100, Sebastian Pipping пишет:
>> How about a monthly bumpday?
>
> Good idea, but it should follow our policy to inform maintainers _in
> advance_: e.g. on first bumpday to work on bumps and notify maintainer
> about this work by attaching final ebuild to the version bump bug with
> clear message that you are going to bump and, _next month_ on bumpday
> it's Ok to commit this ebuild to the tree. Just picking bugs and bumping
> them straight to the tree without knowing why maintainer haven't done
> that yet is a bad idea.
Agreed. However, am I the only one who wouldn't start doing an ebuild
_before_ okay or timeout? Chances are too high to work for the trashcan.
I recommend a plain post of this text to an affected bug:
I hereby request this bug and package to be opened to non-maintainer
bumps. Unless this bug is closed before April's bumpday (2010-04-17)
or any of the maintainer objects I may take the liberty of bumping
this package from April's bumpday on.
Sebastian
prev parent reply other threads:[~2010-03-21 0:59 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
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 [this message]
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=4BA56F4D.5090603@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