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. 

Thanks, 





From:   Denis Roy <denis....@eclipse.org>
To:     Cross project issues <cross-project-issues-dev@eclipse.org>, 
Date:   12/16/2015 01:36 PM
Subject:        [cross-project-issues-dev] Mac signing service issues
Sent by:        cross-project-issues-dev-boun...@eclipse.org



Folks,

The Mac signing service is currently broken. We're tracking the issue in :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=484438

Denis

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to