[meego-packaging] Referencing bug numbers/features
marius.vollmer at nokia.com
Fri Sep 24 01:13:56 PDT 2010
ext Alexander Kanevskiy <kad at kad.name> 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
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
- Fixed-In 0.1: BCM#xxxx.
- 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.
More information about the MeeGo-packaging