Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363982 - Create "integration" branch for equinox.binaries repository?
Summary: Create "integration" branch for equinox.binaries repository?
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Launcher (show other bugs)
Version: 3.8.0 Juno   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-16 17:33 EST by DJ Houghton CLA
Modified: 2011-11-21 14:10 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 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 CLA 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 CLA 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.