1 |
On Wed, Mar 10, 2010 at 6:41 AM, Mark Loeser <halcy0n@g.o> wrote: |
2 |
> Mike Frysinger <vapier@g.o> said: |
3 |
>> On Tuesday 09 March 2010 23:08:24 Sebastian Pipping wrote: |
4 |
>> > We have about 500 bump request open at the moment: |
5 |
>> > https://bugs.gentoo.org/buglist.cgi?quicksearch=bump |
6 |
>> > |
7 |
>> > I assume that quite a few of them would be no big deal to their |
8 |
>> > maintainers in Gentoo. |
9 |
>> > |
10 |
>> > |
11 |
>> > Bugday is occupying the first Saturday of the month: how about bumpday |
12 |
>> > on the third Saturday of the month? First bumpday could be March 20th, |
13 |
>> > 10 days from now. |
14 |
>> > |
15 |
>> > What do you think? |
16 |
>> |
17 |
>> for the maintainer-needed ones, np. for the ones with maintainers, i think |
18 |
>> you need an ack from someone first. |
19 |
> |
20 |
> I don't even think the maintainer-needed ones should be bumped. Who |
21 |
> knows what bugs you are introducing into the tree. This is why things |
22 |
> eventually get treecleaned. |
23 |
> |
24 |
> As Mike said, for ones with maintainers, don't touch them unless you |
25 |
> have explicit permission. We have maintainers for a reason, and if you |
26 |
> don't know the intricacies of the package, you shouldn't be touching it. |
27 |
> You should know how it works, how to test it, and what the normal |
28 |
> problems of a bump are. |
29 |
> |
30 |
> With that being said, I don't really see the point of a bumpday. These |
31 |
> day ideas are ignoring the fact that we don't have enough active developers, |
32 |
> which is the real problem. |
33 |
> |
34 |
|
35 |
We have plenty of developers, the problem is we have too many packages ;p |
36 |
|
37 |
-A |
38 |
|
39 |
> -- |
40 |
> Mark Loeser |
41 |
> email - halcy0n AT gentoo DOT org |
42 |
> email - mark AT halcy0n DOT com |
43 |
> web - http://www.halcy0n.com |
44 |
> |
45 |
> -----BEGIN PGP SIGNATURE----- |
46 |
> Version: GnuPG v1.4.6 (GNU/Linux) |
47 |
> |
48 |
> iD8DBQFLl6+3CRZPokWLroQRAp07AKDgqdRi1gWsIp0wG+QLIaYEXss5OwCdHNZ6 |
49 |
> Owj8ESEixDWVN03OwJV53EQ= |
50 |
> =F2pI |
51 |
> -----END PGP SIGNATURE----- |
52 |
> |
53 |
> |