[off/2] some questions about Malone

Alexander Belchenko bialix at ukr.net
Thu Dec 21 07:42:34 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool пишет:
> On 20 Dec 2006, Alexander Belchenko <bialix at ukr.net> wrote:
>> John Arbash Meinel пишет:
>>> Alexander Belchenko wrote:
>>>> I try to understand best way to work with our bugtracker on Launchpad.
>>>> I have some questions:
>>>> 1) I'm not completely understand statuses of bug. What difference
>>>> between: `Fix Commited' and `Fix Released'? *When* I need to change
>>>> status to `Commited', and *when* to `Released'?
>>> For 'bzr' we follow the rule that:
>>>   In Progress => Someone has started working on a fix
>>>   Fix Committed => Someone has implemented a fix and has committed it to
>>>                    a public branch.
>>>
>>>   Fix Released => This has been merged into bzr.dev
>>>
>>> I'm not 100% happy with that.
> 
> By the way these are documented in http://bazaar-vcs.org/BugGuidelines

Thanks, I missing this guide.
BTW, severity described on this page does not correlate with one on Malone.

>> I'm second here.
>>
>>> As it feels like there should be 4 levels:
>>>
>>>   1) Someone started on it
>>>   2) Someone has submitted a patch
>>>   3) That patch was merged into mainline
>>>   4) That patch is in an official release.
>> I was thinking that step 3 is `Fix Commited' and step 4 is `Fix Released'.
>> But I'll teach first scheme (above). May be it's more easily to manage.
> 
> I agree that would be better, but the problem is that there is no way
> yet afaik to make a batch change of all Committed bugs to Released.
> Changing them all by hand would be too much work.  (Though I heard
> something about an xmlrpc tool that might be a way to do it...)
> Actually it would be even better to automatically link to the revision
> which marks the bug closed, and I think someone is working on that.

Yes, I understand the point of auto-close bugs on real release.
It's just confusing first time, but now I know the reasons, so I use
statuses as defined.

Alexander

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFijrqzYr338mxwCURAqV1AJkB8eV+mVHyA2SmGZfRSp4L/AX8ZgCeMnL2
JcCFaFZM+Y+lnqUF5MwUp3c=
=1KtE
-----END PGP SIGNATURE-----





More information about the bazaar mailing list