From: Michael Vorburger [mailto:[email protected]]
Sent: Thursday, March 16, 2017 10:38 PM
To: Jamo Luhrsen <[email protected]>
Cc: N Vivekanandan <[email protected]>; Sam Hague 
<[email protected]>; <[email protected]> 
<[email protected]>; odl netvirt dev 
<[email protected]>; [email protected]
Subject: Re: [OpenDaylight Discuss] [releng] [netvirt-dev] Fwd: Duplication of 
efforts on same job

On Thu, Mar 16, 2017 at 5:58 PM, Jamo Luhrsen 
<[email protected]<mailto:[email protected]>> wrote:
+ dev and [releng] topic

Is this possible to setup with our tools? to have a BZ comment generated when a
bug is tagged in the commit message? we already get an automatic link in gerrit
when the bug is there.

+1, that would be cool...
... perhaps that is one (of perhaps more) things that would help us to start 
using bugs more?
Other ideas for bugzilla: We seem to be lousy re. using the Version field, or 
is that just me? Most issues (at least those I come across) don't have versions 
set at all. The actual bugzilla "Version" only offers "unspecified" (at least 
e.g. in genius project), and the custom ODL SR Target Milestone dropdown has 
loads of values - hard to link to branches, I find. The "unspecific" IMHO 
should be "Future". Also there's usually two fields, one like "Found in" or 
"affecting" or something like that, and the other "Fixed in" kind of thing.

[Vivek]
++1 for both having a valid version value on bug creation and also Fixed-In 
value indicating the build where the fix merged would be double-great-to-have ☺

Vivek



Thanks,
JamO

On 03/16/2017 09:44 AM, N Vivekanandan wrote:
>
>
> In Openstack, once we raise a review with the bug tagged in commit message, 
> the bug automatically gets a comment appended
> with the review link.
>
>
>
> Would be good to see if something is available that integrates git reviews in 
> OpenDaylight with Bugzilla automatically.
>
>
>
> Vivek
>
>
>
>
>
> *From:*[email protected]<mailto:[email protected]>
>  
> [mailto:[email protected]<mailto:[email protected]>]
>  *On Behalf Of *Sam Hague
> *Sent:* Thursday, March 16, 2017 8:57 PM
> *To:* <[email protected]<mailto:[email protected]>> 
> <[email protected]<mailto:[email protected]>>; odl 
> netvirt dev 
> <[email protected]<mailto:[email protected]>>
> *Subject:* [netvirt-dev] Fwd: Duplication of efforts on same job
>
>
>
> This is good to know across ODL when using bugzilla.
>
> ---------- Forwarded message ----------
> From: *Janki Chhatbar* <[email protected]<mailto:[email protected]> 
> <mailto:[email protected]<mailto:[email protected]>>>
> Date: Thu, Mar 16, 2017 at 9:31 AM
> Subject: [netvirt-dev] Duplication of efforts on same job
> To: odl netvirt dev 
> <[email protected]<mailto:[email protected]>
>  
> <mailto:[email protected]<mailto:[email protected]>>>
>
> Hi
>
> I noticed there is quite some duplication of efforts in working on a bug or 
> submitting a patch. Lets try to minimize this.
>
> Few ways:
>
> 1. If you are working on a bug, please assign it yourself and change the 
> status to "IN_PROGRESS". If you want to work on a
> bug that is assigned to someone else, talk to the person first before 
> reassigning to yourself (even if the status is not
> "IN_PROGESS". Requesting this out of personal experience)
>
> - be clear when using bugzilla so we can get the most use out of it. Assign 
> yourself to a bug and move it to IN_PROGRESS.
>
> - add comments to the bug so others can see the progress.
>
>
>
> 2. If you have a patch against a bug, please post its gerrit link in the 
> comment on the bug. This helps in keeping track.
>
> Thanks
>
> Janki
>
>
> _______________________________________________
> netvirt-dev mailing list
> [email protected]<mailto:[email protected]> 
> <mailto:[email protected]<mailto:[email protected]>>
> https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
>
>
>
>
>
> _______________________________________________
> netvirt-dev mailing list
> [email protected]<mailto:[email protected]>
> https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
>
_______________________________________________
Discuss mailing list
[email protected]<mailto:[email protected]>
https://lists.opendaylight.org/mailman/listinfo/discuss

_______________________________________________
Discuss mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/discuss

Reply via email to