Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363982

Summary:	Create "integration" branch for equinox.binaries repository?
Product:	[Eclipse Project] Equinox	Reporter:	DJ Houghton <dj.houghton>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer, john.arthorne, tjwatson
Version:	3.8.0 Juno
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description DJ Houghton

2011-11-16 17:33:03 EST

As per John's msg:
   http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg09291.html
we are creating integration branches in all our repositories. Do we need to do this for the repo with the launchers? What is our strategy for contributing the launchers to the build?

Comment 1 John Arthorne

2011-11-18 08:53:43 EST

I don't think it is needed. The binaries are fetched purely by a tag that was produced when running the separate launcher build. It doesn't really matter what branch those binaries come from. I think leaving them in master is fine.

Comment 2 Thomas Watson

2011-11-21 14:10:44 EST

(In reply to comment #1)
> I don't think it is needed. The binaries are fetched purely by a tag that was
> produced when running the separate launcher build. It doesn't really matter
> what branch those binaries come from. I think leaving them in master is fine.

I agree, we don't need an integration branch for the binaries.