If we could somehow use an Enterprise Github server at apache then maybe we could get off of jira ...
On Mon, Nov 28, 2011 at 5:02 PM, Ken Wallis <[email protected]> wrote: > Trust me, we really don't want to get into mirroring stuff between github and > jira. We have tried to do that internally at rim before and it is a > nightmare prone to error. > > While I whole-heartedly support GitHub and the integration between commits, > discussions, and issues, it would be better to move completely to Jira if > GitHub is a non option. > > Sorry I missed that bit while lurking on the call. ;) > > ----- Original Message ----- > From: Gord Tanner [mailto:[email protected]] > Sent: Monday, November 28, 2011 06:27 PM > To: [email protected] <[email protected]> > Subject: Re: multiple issue trackers - apache jira, github callback, etc > > The main thing we loose is the ability to reference issues via commit > comments and have them link up automagically. As well as the epic > discussion on those commits / issues / pullrequests. > > Is this an absolute requirement to use JIRA? I see us loosing a LOT of > what makes github awesome by not using its issue tracker. > > Gord > > On Mon, Nov 28, 2011 at 6:20 PM, Filip Maj <[email protected]> wrote: > >> >> >> So, our maintainers will take on the responsibility of mirroring GitHub >> >>issues on JIRA. This includes comments. >> > >> >"This includes comments" seems totally unreasonable. More reasonable >> >would be leaving GitHub issue trackers open, and when a new issue is >> >posted, do the following: >> > >> >- opening a corresponding tracker on Jira >> >- post a link to that tracker in the GitHub issue, and then close the >> >issue >> >> +1 >> >> > > > -- > Gord Tanner > Senior Developer / Code Poet > tinyHippos Inc. > @tinyhippos > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. >
