| 1 |
On Wed, 10 Mar 2010 09:41:59 -0500 |
| 2 |
Mark Loeser <halcy0n@g.o> wrote: |
| 3 |
|
| 4 |
> As Mike said, for ones with maintainers, don't touch them unless you |
| 5 |
> have explicit permission. We have maintainers for a reason, and if you |
| 6 |
> don't know the intricacies of the package, you shouldn't be touching it. |
| 7 |
> You should know how it works, how to test it, and what the normal |
| 8 |
> problems of a bump are. |
| 9 |
|
| 10 |
And if you're already getting the maintainer to take the time to review your |
| 11 |
work and make sure it doesn't break anything they might as well be doing the |
| 12 |
bump themselves. |
| 13 |
|
| 14 |
That said, I think there's still a case for taking action yourself if you |
| 15 |
can't get a response out of the maintainer within a reasonable time and the |
| 16 |
bump is necessary (ie. fixes a real problem, not just because there's a newer |
| 17 |
version out). |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
fonts, by design, by neglect |
| 22 |
gcc-porting, for a fact or just for effect |
| 23 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives