Re: [cross-project-issues-dev] Reminder today is last build for Luna SR1

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

The new build is started but takes 45 minutes.  And I’ll need 15 minutes to promote the bits.

 

David, do you mind waiting an hour for the simrel build?

 

Sorry about that.

 

Marc

 

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: Wednesday, September 17, 2014 3:53 PM
To: 'cross-project-issues-dev@xxxxxxxxxxx'
Subject: Re: [cross-project-issues-dev] Reminder today is last build for Luna SR1 ... and Mars M2 is close!

 

Hi,

 

I’m trying to re-spin the CDT RC4 build due to a major bug we just found.  I’ve requested the ok from the CDT community but I wanted to give a heads up here right away since the aggregation build is very soon.  I’m hoping to have the new CDT build in an hour or two, as quickly as I can.

 

Thanks

 

Marc

 

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, September 17, 2014 10:08 AM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Reminder today is last build for Luna SR1 ... and Mars M2 is close!

 

I'm sure every one knows already, but today (5 PM Eastern, or so) is last aggregation build for Luna SR1 ... then EPP packages will be built ... and next week is "quiet week" ... where the idea is everyone can prepare for the release, update "info center" if needed, do even more testing, especially adopters who want to have their release ready the same time as we do ... etc. One thing to test well is "update", that's always a nasty failure to discover after we have released. For "how to do" see

https://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F

The other thing that's good to check is that the version you think you are contributing, is what actually ends up in the 'maintenance' repo ... and that p2 (and other constraints) don't cause something higher or lower to be picked. Sometimes this "multiple versions" repo report is helpful for quick sanity check (but, nothing beats "manually" checking what is installed from Sim. Release, compared to what is installed from your own repo.
http://build.eclipse.org/simrel/luna/reporeports/reports/nonUniqueVersions.txt

As far as I know, Luna is looking well (everyone is "enabled"), but there are more "errors" in the fundamentals of "repo report" than I'd like to see. I really don't understand why "about files" and "unsigned bundles" are not correct in every contribution? I guess it depends on your releng processes?

http://build.eclipse.org/simrel/luna/reporeports/

If anyone anticipates problems or has any questions, do let us know earlier rather than later!

Thanks,