Stefan Fritsch writes ("Re: security updates introducing breakage"):
> On Thu, 20 Jan 2011, Ian Jackson wrote:
> > An alternative would be to look for bugs which are "fixed" in the
> > previous version but "found" in the update, and ask submitters of
Stefan Fritsch writes ("Re: security updates introducing breakage"):
> Ack. There is no automatic way the security team is notified of such bugs.
> Please CC us in such cases.
Would it be worth defining a [user]tag of some kind that would allow
this kind of thing to be dealt aut
On Thu, 20 Jan 2011, Ian Jackson wrote:
Stefan Fritsch writes ("Re: security updates introducing breakage"):
Ack. There is no automatic way the security team is notified of such bugs.
Please CC us in such cases.
Would it be worth defining a [user]tag of some kind that would allow
th
On Thu, 20 Jan 2011, Adam D. Barratt wrote:
On Thu, January 20, 2011 03:18, Paul Wise wrote:
On Thu, Jan 20, 2011 at 10:59 AM, Brian May
wrote:
What is policy when security updates for stable introduce new
regressions in software that weren't there before? Can these get fixed
in stable?
If
On Thu, January 20, 2011 03:18, Paul Wise wrote:
> On Thu, Jan 20, 2011 at 10:59 AM, Brian May
> wrote:
>
>> What is policy when security updates for stable introduce new
>> regressions in software that weren't there before? Can these get fixed
>> in stable?
>
> If a stable security update contain
On Thu, Jan 20, 2011 at 10:59 AM, Brian May
wrote:
> What is policy when security updates for stable introduce new
> regressions in software that weren't there before? Can these get fixed
> in stable?
If a stable security update contained a regression, usually that is
fixed with an update in the
6 matches
Mail list logo
