| 1 |
On 06/16/2016 03:02 PM, Michał Górny wrote: |
| 2 |
> Hello, everyone. |
| 3 |
> |
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
> |
| 8 |
> What I'd like to introduce instead is a new STABILIZED state. It would |
| 9 |
> -- like VERIFIED now -- be only available for bugs already RESOLVED, |
| 10 |
> and it could be used to signify that the fix has made it into stable. |
| 11 |
> |
| 12 |
> While this wouldn't be really obligatory, it would be meaningful for |
| 13 |
> trackers that need to ensure that fixes in packages have made it to |
| 14 |
> stable -- like the functions.sh use tracker. |
| 15 |
> |
| 16 |
|
| 17 |
The description of InVCS keyword in bugzilla is: |
| 18 |
InVCS Fix has been added to a VCS(either CVS, SVN, Git, ...) |
| 19 |
repository. Will be closed when fixes are applied to a stable level package. |
| 20 |
|
| 21 |
A bug isn't resolved until it is fixed in a stable package (for packages |
| 22 |
ever in stable to begin with), but InVCS keyword can be used by |
| 23 |
developers to filter out the bugs for issues to work with. I oppose a |
| 24 |
change to that behavior, although I would like to see it being used more |
| 25 |
consistently as it seems quite a few developers are neglecting the |
| 26 |
stable tree. |
| 27 |
|
| 28 |
-- |
| 29 |
Kristian Fiskerstrand |
| 30 |
OpenPGP certificate reachable at hkp://pool.sks-keyservers.net |
| 31 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives