Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Are you ready for M5?

We now have sign off from all teams and I've promoted build I20100129-1300  to 3.6M5.  It's now replicating to  I'll be updating the Helios build shortly.


Markus Keller <markus_keller@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

01/30/2010 05:22 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [cross-project-issues-dev] Are you ready for M5?

The risk for further changes is very low. All teams except for p2 have given their Go for I20100129-1300, see

The latest p2 contribution was just an update of the org.eclipse.platform.doc.isv plug-in, which unfortunately caused a minor problem during Javadoc generation.

Even if there is another rebuild, only that doc plug-in will be affected.

Sorry for the rebuild on Friday. I really had to fix that problem -- didn't want to risk another M5a.



From: Thomas Hallgren <thomas@xxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 2010-01-30 09:35
Subject: Re: [cross-project-issues-dev] Are you ready for M5?

Today is the 30th and I still don't see an M5 for the platform. Can we trust that there will be absolutely no changes in the latest I-build? I had planned to do a lot of testing this weekend.

- thomas

On 01/27/2010 07:06 PM, David M Williams wrote:

Just a reminder that M5 is coming up. 2/5 is the very last day of the M5
window ... we all need to meet our contributions before then! ... and the
+0 date is this Friday (1/29). So, not a lot of room for error or delays.

Please keep an eye on your helios contributions, to make sure they can be
aggregated correctly, without error. The expectation is that "breaks" will
be corrected within a few hours. If they can not be, keep us all posted
about outlook here on this list.
If this isn't done, I'd likely have to pull the breaking component out,
plus all its dependents, and that's a whole lot of extra work (for me) and
adds a lot of risk and uncertainty to the milestone (for everyone else).
As always, we will declare on time!

I also wanted to remind you that the deadline for CQ's is the end of M5
(2/5). This is an important deadline since it allows "budgeting" for the
required IP work. CQs submitted after that date may not be (or I should
say will likely not be?) approved in time for Helios and could thus
prevent you from releasing as you plan. So get those CQs submitted! And/or
ask questions (now!) if you have some special case.

Lastly, tracking. We are making some progress on getting an on-line system
to track compliance to requirements, but it will not be done by M5 as I
once fantasized. Thus, I'll prepare a shortened "check list style" version
of  the requirements document,
as some of you have requested. Details later.

Thanks, as always


cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top