https://issues.apache.org/jira/browse/INFRA-8857
On Thu, Dec 11, 2014 at 8:34 AM, Mark Payne <[email protected]> wrote: > I'm +1 to both as well. > > > Date: Thu, 11 Dec 2014 06:46:17 -0500 > > Subject: Re: Commits / Linking to Jira > > From: [email protected] > > To: [email protected] > > > > +1 to 1 and 2. > > > > On Thu, Dec 11, 2014 at 1:07 AM, Joey Echeverria <[email protected]> > wrote: > > > > > +1 to 1 and 2. > > > > > > On Wed, Dec 10, 2014 at 9:32 PM, Joe Witt <[email protected]> wrote: > > > > and by that (submitting now) i mean to ask is there anyone opposed to > > > > this? Part of [1] is to ensure the community is generally in favor > of > > > this. > > > > > > > > Will see if anyone responds negatively and if not will submit the > ticket > > > > tomorrow. > > > > > > > > Specifically i propose we request: > > > > > > > > https://www.apache.org/dev/svngit2jira.html with the trigger > activating > > > on > > > > the present of a NIFI-### anywhere in the commmit message. > > > > and > > > > > > > > https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > > > > that we request the following features > > > > > > > > - Any Pull Request that gets opened, closed, reopened or commented > on now > > > > gets recorded on the project's mailing lis > > > > - If a project has a JIRA instance, any PRs or comments on PRs that > > > include > > > > a JIRA ticket ID will trigger an update on that specific ticket > > > > - Replying to a GitHub comment on the dev@ mailing list will > trigger a > > > > comment being placed on GitHub (yes, it works both ways!) > > > > > > > > Thanks > > > > Joe > > > > > > > > On Thu, Dec 11, 2014 at 12:26 AM, Joe Witt <[email protected]> > wrote: > > > > > > > >> Excellent Sean! Submitting INFRA request now for 1&2 now! > > > >> > > > >> Joe > > > >> > > > >> On Thu, Dec 11, 2014 at 12:19 AM, Sean Busbey <[email protected]> > > > wrote: > > > >> > > > >>> You can have Infra put in a hook that will comment on the > referenced > > > Jira > > > >>> ticket when a commit is pushed to the repo.[1] (you can also > opt-in to > > > >>> having PRs on github trigger jira updates[2]) > > > >>> > > > >>> You can also have those notifications go into the work-log now > instead > > > of > > > >>> as a normal comment. This is nice because it makes it so interested > > > >>> parties > > > >>> can easily filter looking at conversation vs commits[3]. > > > >>> > > > >>> Another common ASF Jira optional feature is the ability to reply to > > > jira > > > >>> notifications and have things show up in the ticket. To do that you > > > have > > > >>> ot > > > >>> request a notification list (usually specific to jira > notifications) > > > and > > > >>> request that it be configured so the reply-to goes to a program > that > > > acts > > > >>> as a bridge from email to jira. > > > >>> > > > >>> [1]: https://www.apache.org/dev/svngit2jira.html > > > >>> [2]: > > > >>> > > > >>> > > > > https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > > > >>> [3]: https://issues.apache.org/jira/browse/INFRA-7873 > > > >>> > > > >>> On Wed, Dec 10, 2014 at 10:44 PM, Joe Witt <[email protected]> > wrote: > > > >>> > > > >>> > What is the best way to ensure that when someone does a commit > that > > > the > > > >>> > Jira ticket for that commit gets updated and for a given Jira > ticket > > > >>> then > > > >>> > one can see updates. Is this sort of trace-ability supported if > we > > > >>> follow > > > >>> > a particular approach? > > > >>> > > > > >>> > Thanks > > > >>> > Joe > > > >>> > > > > >>> > > > >>> > > > >>> > > > >>> -- > > > >>> Sean > > > >>> > > > >> > > > >> > > > > > > > > > > > > -- > > > Joey Echeverria > > > > >
