ext Alexander Kanevskiy <[email protected]> writes: >> There is, however, a difference between a bug that can not be reproduced >> and we might thus have a bug that we haven't fixed, and a bug that is >> known and fixed already, and we can forget about it. We might want to >> distinguish these in Bugzilla. > > We might not. If we can't link code changes to reported issue, there > is no value of having information on "non-reproducible anymore in that > version" bugs.
We can link code changes to reported issues, even if the issue is reported after the code change has been released. That's what I wanted to 'enable' with my proposal. Instead of resolving the bug as WORKSFORME without any trace to the code change that fixed it, we resolve it as FIXED and create that link post factum. By having a convention for how to markup fixes in earlier versions in .changes, the machine can create a correct comment in Bugzilla, even if the markup appears in a later version. So maybe we should make it more machine readable: - Fixed-In 0.1: BCM#xxxx. Or maybe: - Fixes: BCM#xxx (in 0.1), BCM#xxx (in 0.2). Or we just don't make a special syntax for this and accept that the Bugzilla comments will not mention the right version. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
