Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Rich Freeman <rich0@g.o>
Subject: Re: pushing fixes to stable before closing bugs
Date: Sat, 12 May 2012 12:28:03 -0400
On Sat, May 12, 2012 at 6:34 AM, "Paweł Hajdan, Jr."
<phajdan.jr@g.o> wrote:
> The idea is that if you only fix in ~arch, you risk a serious and
> _known_ regression in stable, which could be easily avoided.

How can you have a regression in stable if stable has the bug already?
 A regression is when you have a stable package with a bug, then you
introduce a new stable package that doesn't have that bug, and then
you introduce yet another new stable package that has the same bug
back again.

While I can see some value in tracking whether bugs have made it to
stable yet, I think we need better tools if we want to do that.
Otherwise it is a big housekeeping mess tracking what is and isn't in
stable yet.

I see the value when we're talking about security bugs, or very
critical bugs, but for the run-of-the-mill minor issues that are the
majority of bug reports I don't see the value in keeping bugs open for
a month or two just to track that the inevitable hasn't happened yet.

Rich


References:
pushing fixes to stable before closing bugs
-- Paweł Hajdan, Jr.
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: pushing fixes to stable before closing bugs
Next by thread:
Re: pushing fixes to stable before closing bugs
Previous by date:
Re: pushing fixes to stable before closing bugs
Next by date:
Proposal of accepting arguments to `default` in src_install (and more?) phases in EAPI=5 (for the next council meeting?)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.