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

Bug 411613

Summary: Start 4.3-M-builds
Product: [Eclipse Project] Platform Reporter: David Williams <david_williams>
Component: RelengAssignee: David Williams <david_williams>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, irbull, john.arthorne, pwebster, Szymon.Brandys
Version: 4.3   
Target Milestone: 4.3.1   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 409686    

Description David Williams CLA 2013-06-25 11:07:55 EDT
While not "needed" for a while, we just as well start-up 4.3-M builds. 

Assuming for now they will occur at 10 AM on Tuesday's, following pattern from previous cycles. 

These builds will use a branched version of eclipse.platform.releng.aggregator (branched to R4_3_maintenance). In that branch, we will leave the eclipse-platform-parent pom versioned as 4.3.0-SNAPSHOT so there is no need for others to change that version in your own maintenance branches. 

It is highly recommended that all teams create an R4_3_maintenance branch of code, to be used in repositories.txt file. 

If anyone is "opposed" to doing that ... in principle, we can use your "tagged" version of the repo in repositories.txt ... that is, we'd use tag R4_3_0 instead of branch R4_3_maintenance. Please document in this bug if you plan to NOT branch your code. Otherwise, I will start off assuming all repositories in repositories.txt should be changed to R4_3_maintenance. 

As reminder to myself, I also need to change "comparator repo" to 4.3-M-builds.
Comment 1 Dani Megert CLA 2013-06-26 06:37:13 EDT
(In reply to comment #0)
> While not "needed" for a while, we just as well start-up 4.3-M builds. 
> 
> Assuming for now they will occur at 10 AM on Tuesday's, following pattern
> from previous cycles. 

In previous years it was always Wednesday 08:00, except last year where we had two streams (built also on Wednesday at 10:00 and 12:00).


>  we'd use tag R4_3_0 instead 

The tag must be R4_3.
Comment 2 David Williams CLA 2013-06-29 17:10:41 EDT
Wed. at 8:00 is fine by me. 

Current state of "branching" vs. tags: That is, current contents of repositories.txt file. 

rt.equinox.binaries: R3_9_maintenance
rt.equinox.bundles: R3_9_maintenance
rt.equinox.framework: R3_9_maintenance 
rt.equinox.p2: R4_3
eclipse.jdt.core.binaries: R4_3_maintenance 
eclipse.jdt.core: R4_3_maintenance
eclipse.jdt.debug: R4_3_maintenance 
eclipse.jdt: R4_3_maintenance 
eclipse.jdt.ui: R4_3_maintenance 
eclipse.pde: R4_3_maintenance 
eclipse.pde.build: R4_3_maintenance 
eclipse.pde.ui: R4_3_maintenance 
eclipse.platform.debug: R4_3_maintenance 
eclipse.platform.resources: R4_3 
eclipse.platform: R4_3_maintenance 
eclipse.platform.common: R4_3_maintenance 
eclipse.platform.releng: R4_3_maintenance 
eclipse.platform.runtime: R4_3_maintenance 
eclipse.platform.swt: R4_3_maintenance
eclipse.platform.swt.binaries: R4_3_maintenance
eclipse.platform.team: R4_3 
eclipse.platform.text: R4_3_maintenance 
eclipse.platform.ua: R4_3_maintenance 
eclipse.platform.ui: R4_3_maintenance 

Presumably rt.equinox.p2 should be branched to R3_9_maintenance. 

Not sure if "resources" and "team" were deliberately left unbranched?
Comment 3 David Williams CLA 2013-06-29 17:14:08 EDT
Ian, I assume it'd be you that'd branch rt.equinox.p2?

Following Tom's pattern for Equinox, assume you'd also be "different" and use 
R3_9_maintenance (instead of R4_3_maintenance, like those in Eclipse Platform). 

Let me know if you need help.
Comment 4 David Williams CLA 2013-06-29 17:15:19 EDT
John, assuming it'd be your decision to branch, or not, 'resources' and 'team' projects? Not sure who is "in charge" of those components.
Comment 5 David Williams CLA 2013-07-02 17:38:02 EDT
I think for right now, I'll stick with using same Hudson test jobs for both. 

Even in the past, the Hudson jobs were always "the same" between branches, they just had different names, so that on platforms that allowed it (linux and macs) we could "run tests in parallel" when we got busy, especially with respins, etc. 

We may need that eventually, but think I'll wait as long as possible before "duplicating" work. Off hand, doubt we'll need "parallel testing" ... except perhaps around those times when milestones and SR releases are near each other.
Comment 6 John Arthorne CLA 2013-07-03 10:58:24 EDT
(In reply to comment #4)
> John, assuming it'd be your decision to branch, or not, 'resources' and
> 'team' projects? Not sure who is "in charge" of those components.

Szymon is. Might be fine here to use the tag and only branch when needed.
Comment 7 David Williams CLA 2013-07-03 18:32:11 EDT
(In reply to comment #6)
> (In reply to comment #4)
> > John, assuming it'd be your decision to branch, or not, 'resources' and
> > 'team' projects? Not sure who is "in charge" of those components.
> 
> Szymon is. Might be fine here to use the tag and only branch when needed.

Yes, and looks like we are there already :) ... to fix bug 412233 both 
'team' and 'p2' will need to be branched. Leaving only 'resources' unbranched.
Comment 8 Dani Megert CLA 2013-07-09 05:09:47 EDT
> Not sure if "resources" and "team" were deliberately left unbranched?

I've branched 'eclipse.platform.team' and updated the 'repositories.txt' file.
Comment 9 Ian Bull CLA 2013-07-11 14:05:08 EDT
p2 has been branched. Sorry for the delay. It's called R3_9_maintenance

Thanks to John for twiddling the git hook for me.

http://git.eclipse.org/c/equinox/rt.equinox.p2.git/log/?h=R3_9_maintenance
Comment 10 Dani Megert CLA 2013-07-16 11:46:10 EDT
(In reply to comment #8)
> > Not sure if "resources" and "team" were deliberately left unbranched?
> 
> I've branched 'eclipse.platform.team' and updated the 'repositories.txt'
> file.

I've branched 'eclipse.platform.resources' and updated the 'repositories.txt' file.

==> all our repositories are now branched.