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: "Paweł Hajdan, Jr." <phajdan.jr@g.o>
Subject: pushing fixes to stable before closing bugs
Date: Sat, 12 May 2012 12:34:23 +0200
I noticed a general tendency to close bugs affecting stable before
pushing the fix to stable.

One recent example is <https://bugs.gentoo.org/show_bug.cgi?id=399291>,
but there are more.

The idea is that if you only fix in ~arch, you risk a serious and
_known_ regression in stable, which could be easily avoided.

Do you have any ideas how do we:

1. Make as many developers (everyone?) as possible aware of this.

2. Handle already closed bugs with no fix in stable? I've seen people
closing the bugs again.

Paweł

Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: pushing fixes to stable before closing bugs
-- Andreas K. Huettel
Re: pushing fixes to stable before closing bugs
-- Andreas K. Huettel
Re: pushing fixes to stable before closing bugs
-- Rich Freeman
Re: pushing fixes to stable before closing bugs
-- Pacho Ramos
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
intel (icc,mkl...) packages looking for new maintainer
Next by thread:
Re: pushing fixes to stable before closing bugs
Previous by date:
intel (icc,mkl...) packages looking for new maintainer
Next by date:
Re: pushing fixes to stable before closing bugs


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.