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?

Although your signing is probably done by now, I've increased the load threshold from 10 to 20.  10 was a bit conservative, and the build machine can take the stress.


On 01/28/2010 03:23 AM, Thomas Hallgren wrote:
My greatest struggle right now is that I just cannot get a build to go through at The signer more or less constantly say:

"Too busy to sign.  Going to sleep."

This, of course, makes it hard to get things ready.

Thomas Hallgren

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@xxxxxxxxxxx

_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx

Back to the top