Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Use of GitHub Issues by Eclipse Projects


Does this extend to Simultaneous Release Projects?

I consider it very important that a Bugzilla search for a problem class name discover all reports concerning that class.

I deally Eclipse's Bugzilla would be extended by a crawler to Github Issues.


        Ed Willink

On 10/11/2015 03:24, Mike Milinkovich wrote:

Several years ago the Eclipse Foundation started allowing its projects to host their day-to-day development at GitHub. As part of that, we implemented several processes to ensure that Eclipse projects could maintain their freedom of action should GitHub ever go away, or dramatically alter their terms of service. A number of the projects which host their development at GitHub subsequently asked if they could also start using GitHub Issues, rather than Bugzilla for tracking issues.

I am pleased to announce that at last week's Board meeting, the Eclipse Foundation approved the following two resolutions:

Resolved, that with PMC approval, the Board approves the use of GitHub Issues for Eclipse projects which are hosted at GitHub. The EMO is instructed to backup GitHub Issues data on server infrastructure to ensure the future freedom of action of these projects.

Resolved, the EMO is instructed to provide instructions to Eclipse projects hosted on GitHub on how to properly utilize GitHub features (e.g. Release Pages) to remain compliant with the Eclipse project branding requirements, Eclipse Development Process, and the Eclipse IP Policy.
This does not mean that you can start using GitHub Issues for your project right away. It does mean that the EMO has started working on a plan to enable that, and we hope to do so soon. Please follow bug 481771 if you are interested in progress on this.

Mike Milinkovich
+1.613.220.3223 (mobile)

_______________________________________________ mailing list

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.

Back to the top