[MidoNet] Branching names
devvesa at gmail.com
Wed Nov 5 16:45:36 UTC 2014
Yes, I confused Jira codenames with Midokura Jira. Let's say MNA-*.
All I would want to see it to know which bug/feature I am going
to review without the need of click into the patch. And also have some kind
of conventions to control the gerrit patches/Jira issues relationship.
So, +1 to add [MNA-xxx] in the commit tittle. It is ok to me.
On 5 November 2014 12:12, Guillermo Ontañón <guillermo at midokura.com> wrote:
> Hi Jaume,
> That's a good idea but beware that those MN- id's belong to Midokura's
> private Jira. I'm not against using that in our commits, but I
> wouldn't add it to the OSS project instructions unless we point to the
> community Jira.
> Apart from that: having the issue ID in the commit msg is more
> important because that's what creates links between the different
> systems and remains in git history.
> On Wed, Nov 5, 2014 at 11:52 AM, Jaume Devesa <devvesa at gmail.com> wrote:
> > Hello midos,
> > I would like to suggest naming conventions to branch names in gerrithub.
> > What
> > do you think about using Jira issues names to identify them in code
> > And
> > differentiate them between bugs and features:
> > bug/MN-#
> > feature/MN-#
> > I can take care of updating the wiki if you are agree
> > : http://wiki.midonet.org/Coding%20Workflow
> > Regards,
> > jaume
> > --
> > Jaume Devesa
> > Software Engineer at Midokura
> > _______________________________________________
> > MidoNet mailing list
> > MidoNet at lists.midonet.org
> > http://lists.midonet.org/listinfo/midonet
Software Engineer at Midokura
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MidoNet