Re: RFC: allow new upstream into stable when it's the only way tofix security issues.

2005-08-03 Thread Anthony DeRobertis
Joe Smith wrote: > How about if it meets the folowing critieria: > > 1. it has been in testing for 10 days (been in sid at least 20 days) This means the security hole was disclosed at least 20 days ago, probably more. > 2. Iff it fixes a critical security problem, uploaded to security (This > re

Re: RFC: allow new upstream into stable when it's the only way tofix security issues.

2005-08-02 Thread Philipp Kern
On Tue, 2005-08-02 at 17:19 -0400, Joe Smith wrote: > I think the no new upstream versions is stable rule needs to be more > flexible anyway. I have seen times where EVERY SINGLE change except for the > version number have been backported. That is often the case where the new > release consists

Re: RFC: allow new upstream into stable when it's the only way tofix security issues.

2005-08-02 Thread Joe Smith
How about if it meets the folowing critieria: 1. it has been in testing for 10 days (been in sid at least 20 days) 2. the version is sid is the same as in testing (the maintainer has not found problems in the ten days since it entered testing) 3. and has no RC bugs (no rc bugs reported in the te