It appears there were no other contributions
after picking up these final ones. So 'staging' is now final, again, for
M4. Markus and I will coordinate our "promoting"
these tomorrow, on Friday, and via IM we have agreed 4 PM at the latest. We hope earlier, if we can get the EPP
packages produced, and the majority of them signed off sooner than that.
David M Williams/Raleigh/IBM@IBMUS To:
Cross project issues
12/17/2015 07:04 AM Subject:
Mac signing service issues -- updated plan for M4 Sent by:
Given Mikael's "new news",
and other's requests, I have "re-enabled" the "VALIDATE"
job on Hudson.
It immediately started with these "changes" listed:
Oomph (late) Upgrade Buildship to 1.0.7
I would like to set a deadline of 12 Noon today (Eastern time). I think
it will be a bit rushed, but believe then we can still make M4 available
on Friday, but, let's say we make the repo and EPP packages available by
4 PM on Friday, instead of 10 AM on Friday. I think that will give time
for all the re-work, and sanity checks by EPP Package maintainers and at
the same time "get it over with" before some start their end-of-year
Let me know if any of these times are unreasonable or simply do not work
due to timezone differences. (It is too early in the morning for me to
compute or look them up myself :) ... not to mention, it depends on exactly
who is effected and may need to "rebuild".)
But, unless you hear otherwise, that is our revised plan.
Barbero <mikael@xxxxxxxxxxx> To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>, Date: 12/17/2015
03:23 AM Subject: Re:
[cross-project-issues-dev] Mac signing service issues -- plan
for M4 Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
The signing issue is due to too much difference between the system clock
and the time stamping authority (and for some reason, NTP does not work
the mac signing machine). I manually synched the time on the machine and
the signing now works properly.
Given there is currently "no solution in sight" for this week,
I think the best course of action is to push ahead, and produce M4 as planned,
with affected projects disabling "Mac signing".
Once we have that build "in hand", a) if the user experience
is "really bad", we can reconsider (but as far as know, if they
are doing fresh install, then they have to do that "open" or
"ctrl-open" trick we have used in the past -- that is, in the
past there has been milestones without a Mac signature. b) if enough people
are around next week, to redo contributions with Mac signed, we can do
an M4a deliverable.
But, in either case, since we are between a rock and a hard place, I think
best to try and produce one as planned. Otherwise, we might be well into
January before we could produce one, depending on everyone's holiday schedules.