Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Luna RC1 staging repo is complete.

Just one remark: The Stardust team has removed its reporting features which was based on Birt and was able to successfully contribute its RC1 to the SimRel build. Please also note that the Stardust RC1 build was compiled against the Eclipse Luna M7 repository because of the WTP issues which are now fixed in WTP 3.6.0RC1a. But this should have no affects…





Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von David M Williams
Gesendet: Donnerstag, 22. Mai 2014 05:55
An: cross-project-issues-dev@xxxxxxxxxxx
Betreff: [cross-project-issues-dev] Luna RC1 staging repo is complete.


A little later in the day than usual ... but ... I'm finally as happy with it as I'm going to get.

Be sure to directly test
as well as test various "update" scenarios (such as update from 4.3.2 with the Java 8 patch applied would be a good one to try :)
[To test "updates" with an EPP package, will also require the EPP staging repo ... which I can never recall ... so I'm hoping Markus will announce that, when its ready.]

If no blocking defects found and request-to-respin made, this will be added to .../releases/luna on Friday morning, in composite with M7.

PMCs and Project Leads: be sure to check the "repo reports" at ... I don't think some of you are up to "release candidate" stage yet, judging from "missing legal files" and use of "old" (or no) SUA licenses.  

About BIRT ... I am glad they are back ... congratulations on recovering, but ...
As I said in Bug 432464  now that BIRT has re-joined the train, I was able to re-enable all features of MAT (I do not know if it works ... just that the build did not fail :) but was not able to re-enable 3 of Stardust features. They'll have to get "caught up" with BIRT being back, and, I assume, provide those features for RC2. -- please remember this lesson: If projects agree to be part of "Simultaneous Release" you are agreeing to be "Simultaneous" every milestone ...  and, if you are not, it has "down stream" impact and delays beyond your own project. In this case, we are lucky that Stardust is not holding up someone else (though, could be causing some adopters to have to slip schedules). There are reasons why "Simultaneous" means "always Simultaneous".
I say this not to be critical of BIRT -- we all know, "stuff" happens -- but just to emphasize there are "methods to our madness" and even this little burp reminds me of the ugly pre-Callisto days ... when basic projects would be "out of sync for 6 months or a year after a June release of the Platform .... and adopters (and users) never knew nor could they predict what worked with what.  (Ever wonder why I'm so passionate about the Simultaneous Release -- those were some dark days! :)

As usual, I've disabled the aggregation job to avoid confusion, but will turn it back on Friday around noon.

Good luck on the next 3 RCs (RC4 being THE Final Build). Only one week apart now ... time to clamp down ... not merely ramp down!

Questions welcome.

Thanks to you all for your contributions to Eclipse -- and reading my long note!

Back to the top