Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Pro

[Wayne Beaton <wayne@xxxxxxxxxxx>]

Webmaster/Mike will correct me if I'm misstating.

At this point in time, there is no plan to mirror GitHub issues to Bugzilla or vice versa.

What we plan to do is regularly capture issues from GitHub in a manner that can be used to to import into another issue tracker should that need arise. i.e., we're going to pull the data out using GitHub APIs and cache it on our servers.

There is some discussion here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=442828

Wayne

On 11/11/15 01:25 AM, Greg Wilkins wrote:

On 11 November 2015 at 17:01, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

IMHO as soon as any significant project, Simultaneous Release today, could be any project tomorrow, does not contribute its issues to a Bugzilla search we have an unpleasant fragmentation and degraded reporting/diagnosis capability.

Ed, I agree that having complete information under eclipse infrastructure is important.   Jetty is one of the projects that would like to shift more towards github, but if bugzilla is to remain (as Mike indicated is will), then I think that github issues & comments should be mirrored to bugzilla and perhaps vice versa.

Having a single list of all issues, regardless of source, is valuable.   Currently we are manually creating bugzillas for PRs we receive from guthub, which is only really half a solution. If github ceased to exist, then we'd know an issue had existed, but would lose it's details and comments.   Thus automated mirroring and/or backup to eclipse sounds like a reasonable way to improve/safeguard something that is already happening now (partially) manually.

cheers

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com

_______________________________________________
eclipse.org-project-leadership mailing list
eclipse.org-project-leadership@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation