incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <>
Subject Re: multiple issue trackers - apache jira, github callback, etc
Date Sat, 03 Dec 2011 00:49:00 GMT
An update: I contacted Github about whether it is possible to have the
Github issue tracker "read-only" and this was the reply:

"That's not possible currently, the issue track is either enabled and
read-write or completely disabled and hidden."

So, links to closed issues will 404 unfortunately. For issues that
were still open, on the iOS issues I did put a reference to the old
link for some search engine juice...

On Mon, Nov 28, 2011 at 3:28 PM, Shazron <> wrote:
> If only we could archive/read-only the Github Issue Tracker that would
> be great. I'd rather close down the github issue tracker then having
> to do this work all the time - but no big deal if I still have to.
> I've been copy and pasting the old issues into their new issues -
> almost done (I'm sure you've seen all those notification emails!).
> Tried to use the Github API to get the comments all in one go, but
> it's all in json though, e.g:
> On Mon, Nov 28, 2011 at 3:20 PM, Filip Maj <> 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
>> +1

View raw message