Re: [eclipse.org-planning-council] Reminder of "First Wednesday" PC meet

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

The Platform will not participate in the
respin. We might consider David's suggestion below though. David, do you
know who could confirm your "I believe that should be sufficient"?

Dani



From:      
 David Williams <david_williams@xxxxxxx>
To:      
 eclipse.org-planning-council@xxxxxxxxxxx
Date:      
 05.10.2016 22:03
Subject:    
   Re: [eclipse.org-planning-council]
Reminder of "First Wednesday" PC meeting, 10/5/2016 12 noon
Sent by:    
   eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

On 10/05/2016 03:42 PM, Nick Boldt wrote:
> Just curious... now that the need for a respin has been decided, and
> it's scheduled to be built Monday with availability on Tuesday, is
> there time to slip in a fix for another regression?
>
> Asking about https://bugs.eclipse.org/bugs/show_bug.cgi?id=503305specifically.
>
> Thx,
>
> Nick

In short, I'd say the answer is 'yes', if the Platform and their PMC 
brought if forward and it got the votes with no objections. Keep in mind
the Monday and Tuesday dates were "done" sort of dates, so that
means 
the fix must be a repo that could be used by the process, say, on Thursday.

BUT, an important difference between that case, and the MPC case is that
the MPC case could only be fixed by a respin (due to the way it is 
"included" in the EPP packages.

As far as I know, the Platform itself is a "root feature" in
the EPP 
packages, so if they create their own (new) repository (under 
.../eclipse/updates/4.6) then I believe that should be sufficient for 
users to get the update via "check for updates".

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.