[cross-project-issues-dev] Juno M1 simultaneous release and Eclipse plat

[fgiquel@xxxxxxxxxxxxxxxx]

Hi,

i am currently preparing EMFFacet M1
build for Juno (replacing Nicolas Bros today)
there is something confusing to me about
Eclipse Platform versions 3.8 et 4.2. I probably missed some message about
it...
I see that in org.eclipse.juno.build,
in org.eclipse.juno.build/ep.b3aggrcon, the 4.2 update is used "http://download.eclipse.org/eclipse/updates/4.2milestones/S-4.2M1-201108051200"
It seems to conform to what you say
: "Kim updates the Platform's contribution to 4.2 M1"

There is another  milestone update
site for Eclipse Platform : "http://download.eclipse.org/eclipse/updates/3.8milestones/S-3.8M1-201108031800".


What is the reason Juno M1 is built
on a 4.2 platform rather than a 3.8 platform ?

Thanks in advance.

---------------------------------------------------------------
Fabien GIQUEL
Responsable Développements Nouvelles Technologies
fgiquel@xxxxxxxxxxxxxxxx
Mia-Software
4, rue du Château de l'Eraudiere
44324 NANTES CEDEX 03
---------------------------------------------------------------

David M Williams <david_williams@xxxxxxxxxx>
Envoyé par : cross-project-issues-dev-bounces@xxxxxxxxxxx

11/08/2011 23:19

Veuillez répondre à
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

A	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Objet	Re: [cross-project-issues-dev] Juno .. ready -- wait! back to v 0.1

Contrary to what I first announced,
let's stay on the Aggregator Editor version 0.1 (on Eclipse 3.6) instead
of moving up to 0.2. At least for Juno M1. There is either a bug blocking
us (bug
454527 )
or I've made some sort of error in "converting" our files (or,
both). Either way, there is not enough time to sort that out before M1,
so let's move back to the same version of the b3 Aggregator we use for
Indigo ... and let the fun begin! So, _now_ you can expect lots of errors
to show up, as Kim updates the Platform's contribution to 4.2 M1. 

Sorry for the churn ... greatest thanks. 






From:        David
M Williams/Raleigh/IBM@IBMUS 
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        08/10/2011
02:12 PM 
Subject:        [cross-project-issues-dev]
Juno aggregation builds are ready,        and Indigo
has moved to 'maintenance' 
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

---

The Indigo aggregation builds will now use the 'maintenance' url instead
of 'staging' as we move towards Indigo SR1. 

http://download.eclipse.org/releases/maintenance/

I have setup and started the Juno aggregation builds, using the previously
contributed indigo b3aggrcon files as a starting point. I have promoted
the initial Juno test-build to the staging repo, and confirmed the current
results are nearly identical, as would be expected. 

http://download.eclipse.org/releases/staging/


There are a few things to point out: 

* If anyone was in Indigo, but will no longer be in Juno, please let us
know, so we can remove your project files sooner rather than later. 

* The Indigo builds will continue to use the 0.1.x version of the b3 aggregator,
installed on Eclipse 3.6, whereas the Juno builds will use the 0.2.x version,
installed on Eclipse 3.7. You can get these aggregator versions from different
b3 repos, respectively: 

http://download.eclipse.org/modeling/emft/b3/updates-3.6/
http://download.eclipse.org/modeling/emft/b3/updates-3.7/

For this reason, I recommend you keep separate instances of Eclipse-aggregator-workspaces,
one for Indigo, and one for Juno to avoid issues or confusion. 

Other than that, and the usual name changes, the procedure for Juno is
like last years. See http://wiki.eclipse.org/Juno/Contributing_to_Juno_Build.

I expect next week to be busy, since we are doing our first Indigo SR1
RC1 (warm-up) build, at the same time we will be creating Juno M1. 

Speaking of dates, the Planning Council has finalized the milestone dates
for Juno, as documented at 

http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates

I will update the google calendar soon. The only change from previous version
was the M6 end date and M7 start date change by 1 week, so they'd each
be a balanced 7 weeks now, and fit in better with EclipseCon. 


Questions welcome. 


_______________________________________________
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