| 1 |
El sáb, 12-05-2012 a las 12:34 +0200, "Paweł Hajdan, Jr." escribió: |
| 2 |
> I noticed a general tendency to close bugs affecting stable before |
| 3 |
> pushing the fix to stable. |
| 4 |
> |
| 5 |
> One recent example is <https://bugs.gentoo.org/show_bug.cgi?id=399291>, |
| 6 |
> but there are more. |
| 7 |
> |
| 8 |
> The idea is that if you only fix in ~arch, you risk a serious and |
| 9 |
> _known_ regression in stable, which could be easily avoided. |
| 10 |
> |
| 11 |
> Do you have any ideas how do we: |
| 12 |
> |
| 13 |
> 1. Make as many developers (everyone?) as possible aware of this. |
| 14 |
> |
| 15 |
> 2. Handle already closed bugs with no fix in stable? I've seen people |
| 16 |
> closing the bugs again. |
| 17 |
> |
| 18 |
> Paweł |
| 19 |
> |
| 20 |
|
| 21 |
I guess it depends in how major is the fixed bug, if it's not too major, |
| 22 |
I think we can wait for next stabilization round (we tend to do it in |
| 23 |
gnome team) |
Archives