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: Pacho Ramos <pacho@g.o>
Subject: Re: pushing fixes to stable before closing bugs
Date: Sat, 12 May 2012 12:50:38 +0200
El sáb, 12-05-2012 a las 12:34 +0200, "Paweł Hajdan, Jr." escribió:
> 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ł
> 

I guess it depends in how major is the fixed bug, if it's not too major,
I think we can wait for next stabilization round (we tend to do it in
gnome team)
Attachment:
signature.asc (This is a digitally signed message part)
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:
pushing fixes to stable before closing bugs
Next by thread:
Re: pushing fixes to stable before closing bugs
Previous by date:
pushing fixes to stable before closing bugs
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.