Re: [cross-project-issues-dev] Status and outlook for M7
Oh, ok ... that's just the difference between Friday evening (when I last promoted to staging) and Sunday afternoon (or, when ever you checked ... job 356 appears to have ran on Saturday).
> I am not familiar with
> overall release aggregator, staging and promotion flow.
The overall flow is that a change to an aggregation file (committed to CVS) will automatically kick off a new aggregation within 15 minutes or so.
If you have your aggregation file set up to "get the latest" from your repo, without any changes to the file itself, as you do, then you either need to start the Hudson aggregation job yourself, or, wait until someone else kicks off an aggregation.
But, in any case, I update "staging" only once a day or so during busy periods ... or, upon request.
Igor Fedorenko ---05/06/2012 09:00:39 PM---I am expecting m2e 220.127.116.1120505-1126 . I see this version mentioned in juno.runAggregator job #356
From: Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
Date: 05/06/2012 09:00 PM
Subject: Re: [cross-project-issues-dev] Status and outlook for M7
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
I am expecting m2e 18.104.22.16820505-1126 . I see this version mentioned in
juno.runAggregator job #356 , but staging repository contains an
older version 22.214.171.12420320-0058. Unfortunately, I am not familiar with
overall release aggregator, staging and promotion flow, so any pointers
where to start investigation will be much appreciated.
On 12-05-06 5:54 PM, David M Williams wrote:
> > ... contain older version of m2e. Is this
> > expected at this point or should I start investigating?
> I'd investigate. I assume you are expect something later than 1.1.0?
> Looks like your m2e.b3aggrcon file has not been updated since November
> of last year? (When it was changed from 1.0.0, to 1.1.0).
> Inactive hide details for Igor Fedorenko ---05/06/2012 04:41:01
> PM---Hello, David, Staging repository  appears to contain olIgor
> Fedorenko ---05/06/2012 04:41:01 PM---Hello, David, Staging repository
>  appears to contain older version of m2e. Is this
> From: Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
> To: cross-project-issues-dev@xxxxxxxxxxx,
> Date: 05/06/2012 04:41 PM
> Subject: Re: [cross-project-issues-dev] Status and outlook for M7
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
> Hello, David,
> Staging repository  appears to contain older version of m2e. Is this
> expected at this point or should I start investigating?
>  http://download.eclipse.org/releases/staging/
> On 12-05-06 3:38 PM, David M Williams wrote:
> > Yes ... its here, M7 week! And, I'm already giving status!
> > First thing to note it that we now have a stand-alone 4.2 primary build
> > from the Eclipse Project, so for the first time we have a pure and
> > correct 4.2 repo. In the past, some things from 3.8 were "slipping in"
> > through aggregation due to the way the platform was producing and
> > partially (unknowingly) combining 3.8 and 4.2. But no more, 4.2 only.
> > One impact of this, is the bundle 'org.eclipse.help.appserver' is no
> > longer available ... it was actually removed in 4.1, but it is being
> > left in the 3.x stream, even though 3.8 does not use it. It now
> > correctly does _not_ show up in 4.2 repo via aggregation.
> > And, this "broke" BIRT ... so, I disabled that, which rippled across 3
> > or 4 others that depend on BIRT charting.
> > I hope BIRT can live without that old bundle and use the jetty server
> > now provided by the platform (and used by the help system, in both 3.8
> > and 4.2).
> > Then there were the (fairly) usual breakages in RAP runtime and Virgo
> > based on assumptions on certain platform specific versions, so I
> > disabled those to get a green build, and promote an initial M7 version
> > to staging. Be sure to check the reports (based on staging) to get as
> > much cleaned up as possible before M7:
> > http://build.eclipse.org/juno/simrel/reporeports/
> > In all, the following files have disabled repositories or features. It
> > looks worse than it is, but we need to get in completely "enabled" in
> > the next few days (or, remove it, if its some old thing that should not
> > even be there any longer).
> > amp.b3aggrcon
> > birt.b3aggrcon
> > emf-compare.b3aggrcon
> > equinox.b3aggrcon
> > jetty.b3aggrcon
> > linuxtools.b3aggrcon
> > mat.b3aggrcon
> > mdt-papyrus.b3aggrcon
> > mft.b3aggrcon
> > rap.b3aggrcon
> > riena.b3aggrcon
> > scout.b3aggrcon
> > virgo.b3aggrcon
> > As always questions and clarifications are welcome.
> > Thanks everyone,
> > _______________________________________________
> > 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 mailing list
cross-project-issues-dev mailing list