What would the workflow be with the new jira and gerrit integration? And what best-practices should be used when creating commit messages?
Typically users have included the bug-id in the beginning of the summary line. That eats up some of the 50 characters allowed so it isn't good. Should we encourage something more like what openstack is doing in [1] where they suggest adding lines in the message themselves like "Closes-Bug: #####", "Partial-Bug: #####"? This seems better and gives more space to the commit-message summary line. Thanks, Sam [1] https://docs.openstack.org/infra/manual/developers.html#development-workflow On Wed, Apr 4, 2018 at 9:50 PM, Michael Vorburger <[email protected]> wrote: > On Thu, Apr 5, 2018 at 2:08 AM, Robert Varga <[email protected]> wrote: > >> On 04/04/18 23:46, Rob Garth wrote: >> > What: The Linux foundation will be performing a migration of the ODL >> > Jira from our data center in Portland to a new instance in AWS. >> > >> > When: Sunday, April 8, 2018 @ 16:00 - 18:00 PT (23:00 - 01:00 UTC) >> > >> > Why: This move will allow us to enable gerrit integration in Jira >> > >> > Impact: Jira will be offline for the maintenance window >> > >> > If there any questions, concerns or requests related to this please >> > let me know, or open a helpdesk ticket related to it. >> >> I can't wait to see the integration working :) >> > > if the helpdesk ticket I raised yesterday to suggest this prompted > JIRA/Gerrit integration, then ... thank you for the amazing.. "time to > market" on this! > > Tx, > M. > -- > Michael Vorburger, Red Hat > [email protected] | IRC: vorburger @freenode | ~ = http://vorburger.ch > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/discuss > >
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
