[development] Perm for setting RTBC - Re: RTBC - how does it work?

Gerhard Killesreiter gerhard at killesreiter.de
Mon Jul 2 18:20:19 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fernando Silva schrieb:
> On 7/2/07, Gerhard Killesreiter <gerhard at killesreiter.de> wrote:
>> If all the people who have written on this list today would instead just
>> have spent some time in the patch queue, Drupal would be better
>> tomorrow...
> 
> It's not exactly like you say, specially when there are people that
> work on the issue queue, and that are never taken serious by core
> developers (whatever the reason is).

Maybe the experience was that the patches weren't worth the time or it
was coincidence.

> BTW, some of the items you marked as "won't fix" have more than an
> year, and none of you had time to commit it before 4.6 died.

They were marked "rtbc" 5 days before 5.0 was released and 4.6 died.

Also, we've only had a dedicated core committer for each release as of
4.7, so, yes, all releases before 4.7 didn't get that much attention
after they had been released.

> It's
> easy, to close issues that way.

Yes, that's why I did it. You could have done it too.

> Life is like this, _some_ influent guys do not deserve their position
> because they do not respect others in any way! Bah...

What reply do you want for that?

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGiUHjfg6TFvELooQRAvUxAJ97ZSuU+TJhZfFs/NtsgGy1vfG9gwCeNuNG
l8QaYcNlHEkRFYaZsYGwsCs=
=+PfM
-----END PGP SIGNATURE-----


More information about the development mailing list