Re: [Aqsis-development] staging website changes
Brought to you by:
ltatkinson,
pgregory
From: Paul G. <pgr...@aq...> - 2012-04-07 18:07:01
|
I don't see this as an issue, the Jira ticket is related to the mainline, i.e. our master. So the ticket is only closed when it is integrated. Any work that happens on separate forks, that require comments and/or references in Jira just need to have a link to the fork included. Paul On 7 April 2012 07:17, Chris Foster <chr...@gm...> wrote: > On Tue, Mar 27, 2012 at 12:46 AM, Josh Stratton > <str...@gm...> wrote: > > I won't bother testing github's functionality as it seems pretty well > > documented. > > > > https://github.com/blog/957-introducing-issue-mentions > > > > I had Paul push a test commit to the aqsis repo with a jira ticket > > name in the commit message, and the commit shows up in the jira ticket > > under the "Commits" tab (see attached image). > > Looks good. One additional question to consider is how this works with > mulitple repos (github encourages everyone to work in thier own fork > after all, and submit pull requests back to the main project). > > To me this sounds like a tricky thing for jira to handle, since it > probably doesn't automatically have knowledge of other repos which are > forks of the main one... (Not that I really know how github handles this > yet.) > > ~Chris > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Aqsis-development mailing list > Aqs...@li... > https://lists.sourceforge.net/lists/listinfo/aqsis-development > |