| 1 |
On Fri, Jun 17, 2016 at 3:37 AM, Alexander Berntsen <bernalex@g.o> wrote: |
| 2 |
> |
| 3 |
> I would not want to tie our choosing RESOLVED to be tied to whether |
| 4 |
> there is a stabilised package in the tree or not, because there are |
| 5 |
> other Portage users than Gentoo. But I would not oppose such an |
| 6 |
> enforcement too strongly at this time. |
| 7 |
> |
| 8 |
|
| 9 |
There is clearly more than one way to approach this. I think the key |
| 10 |
is to get everybody to do it the same way. |
| 11 |
|
| 12 |
I do agree that it is overkill to track EVERY bug through to stable. |
| 13 |
However, I can see the value in tracking some bugs through to stable. |
| 14 |
The question is how do we tell which are which, and ensure the ones |
| 15 |
that need to be tracked are actually updated when the package is |
| 16 |
stabilized? |
| 17 |
|
| 18 |
It might be better to just close the original bug, and then open a new |
| 19 |
STABLEREQ bug on the tracker whenever we're interested in tracking |
| 20 |
stabilization. That also serves as a reminder to the maintainer that |
| 21 |
somebody actually wants it stabilized. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Rich |
Archives