Re: [cross-project-issues-dev] Concluding SR2 RC1 warm-up repository

[David M Williams <david_williams@xxxxxxxxxx>]

Well, that's why we do a warmup :) 

Did you meant to contribute .../tm/updates/3.4
to Juno or ... /tm/updates/3.4milestones?


I see the former in 'master' and later
in 'Juno_maintenance'. I can't tell by the names, but often XXMilestones
implies something older than XX repository? You need to use the Juno_maintenance
branch of  org.eclipse.simrel.builds project. 

HTH




From:      
 David Dykstal/Rochester/IBM@IBMUS
To:      
 Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 01/17/2013 11:19 AM
Subject:    
   Re: [cross-project-issues-dev]
Concluding SR2 RC1 warm-up repository
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

It looks like my first attempt at contributing
to the aggregation build failed. If I'm reading the reports correctly I
see the TM SR1 plugins there rather than the ones from the repository I
thought I had contributed. Obviously my understanding of how the contribution
files work is incorrect. 

Can someone give me a hand here and look at tm.b3aggrcon?

-- David Dykstal,  Architect - Rational Developer for Power Systems



From:        David
M Williams/Raleigh/IBM@IBMUS 
To:        "Cross
project issues (cross-project-issues-dev@xxxxxxxxxxx)" <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        01/17/2013
08:39 AM 
Subject:        [cross-project-issues-dev]
Concluding SR2 RC1 warm-up repository 
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Sorry, fell asleep last night :) when I should have been sending out this
notice. 

But, we are done with SR2 RC1 warm-up repo. 

Remember its "staging" location is 
http://download.eclipse.org/releases/maintenance/

Besides testing that repo, be sure to check the repository reports ...
looks like a few regressions for required files, signed jars, etc. 
http://build.eclipse.org/simrel/juno/reporeports/

In addition to testing only that single repo, be sure to test it as a "composite",
since eventually it will be added to .../releases/juno
as a child repository. See 
http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#Test_staging_as_a_pseudo_composite
Don't forget to test "update" scenarios (some of which need to
wait for EPP repositories to be ready, if they are not already). 

Recall that there is no "promotion" of this repo. It will simply
be "left alone" for about a week ... until Juno SR2 RC2 +0. 
http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#SR2

As a "warm-up", we don't expect this to be a true "release
candidate", but please approach RC2, RC3, etc., with the attitude
that those will be true "release candidates" suitable for adopter
acceptance testing, etc. 

Thanks, 
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev