| 1 |
On 03/19/10 13:36, Peter Volkov wrote: |
| 2 |
> В Срд, 10/03/2010 в 05:08 +0100, Sebastian Pipping пишет: |
| 3 |
>> How about a monthly bumpday? |
| 4 |
> |
| 5 |
> Good idea, but it should follow our policy to inform maintainers _in |
| 6 |
> advance_: e.g. on first bumpday to work on bumps and notify maintainer |
| 7 |
> about this work by attaching final ebuild to the version bump bug with |
| 8 |
> clear message that you are going to bump and, _next month_ on bumpday |
| 9 |
> it's Ok to commit this ebuild to the tree. Just picking bugs and bumping |
| 10 |
> them straight to the tree without knowing why maintainer haven't done |
| 11 |
> that yet is a bad idea. |
| 12 |
|
| 13 |
Agreed. However, am I the only one who wouldn't start doing an ebuild |
| 14 |
_before_ okay or timeout? Chances are too high to work for the trashcan. |
| 15 |
|
| 16 |
I recommend a plain post of this text to an affected bug: |
| 17 |
|
| 18 |
I hereby request this bug and package to be opened to non-maintainer |
| 19 |
bumps. Unless this bug is closed before April's bumpday (2010-04-17) |
| 20 |
or any of the maintainer objects I may take the liberty of bumping |
| 21 |
this package from April's bumpday on. |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
Sebastian |
Archives