Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
On 05/31/2012 10:52 PM, Mehdi Dogguy wrote:
> Please note that "badly maintained" is something quite different from
> "not maintained". AFAICS, the package we are talking about is not
> affected by severe or critical bugs.
That's a mater of views. #470294 should be made RC IMO.
Or is writing to /usr not a good candidate for an RC bug?
I thought this was a "serious violation of the policy". Am I wrong?
Cheers,
Thomas
Reply to:
- References:
- Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Thomas Goirand <zigo@debian.org>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Jonas Smedegaard <dr@jones.dk>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Thomas Goirand <thomas@goirand.fr>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Jonas Smedegaard <dr@jones.dk>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Charles Plessy <plessy@debian.org>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Jonas Smedegaard <dr@jones.dk>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Thomas Goirand <zigo@debian.org>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Jonas Smedegaard <dr@jones.dk>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Thomas Goirand <zigo@debian.org>
- Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
- From: Mehdi Dogguy <mehdi@dogguy.org>