JIRA protocol

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

JIRA protocol

demiankatz

Is there documentation on ZF’s use of JIRA anywhere?

 

The Git guide suggests naming branches after JIRA tickets, so I opened a new ticket (ZF2-399) yesterday in combination with submitting a PR.

 

I see now that the PR has been accepted (thanks!) but the ticket is still open.  Should I close it now?  Should I have opened or assigned it in a different way to make things happen automatically?  I just want to be sure I’m not creating unnecessary work for anyone else.

 

thanks,
Demian

Reply | Threaded
Open this post in threaded view
|

Re: JIRA protocol

akrabat
<base href="x-msg://70/">Hi,

We're a bit fluid on our use of JIRA at the moment. 

In general, I would raise a JIRA ticket if you need to note a problem because you're not going to be fixing it "right now". However, if you notice something and fix it immediately, then just call your branch something like hotfix/fix-for-xxx. 

In an ideal world, the person who merges the branch would close the JIRA ticket, but that doesn't always happen, so feel free to close it yourself with a comment with the PR link in it.

Of course, this may change over time, but we're not going to refuse a PR just because there isn't a JIRA ticket for it :)

Regards,

Rob...


On 17 Jul 2012, at 14:52, Demian Katz wrote:

Is there documentation on ZF’s use of JIRA anywhere?
 
The Git guide suggests naming branches after JIRA tickets, so I opened a new ticket (ZF2-399) yesterday in combination with submitting a PR.
 
I see now that the PR has been accepted (thanks!) but the ticket is still open.  Should I close it now?  Should I have opened or assigned it in a different way to make things happen automatically?  I just want to be sure I’m not creating unnecessary work for anyone else.
 
thanks,
Demian