|Re: [cross-project-issues-dev] MPC Readinness (about Re: [eclipse-pmc] Upgrading the Eclipse SDK target environment for the *September* Eclipse release...)|
current focus of the MPC development is implementing support for the new marketplace API (https://github.com/EclipseFdn/marketplace-rest-api#eclipse-foundation-marketplace-client-api). That is the reason why there was not much activity on the Git repo (at least on master).
But I was planning to build a MPC release for 2020-06 anyhow, and I agree, that your patch should be integrated. So, I hope I can do the review this weekend and integrate the patch in the M3 MPC release.
Thanks for the reminder.
To prepare the upcoming move to Java 11 as BREE during the 2020-06->2020-09 update, we've added to p2 (opt-out) additional checks preventing the installation of bundles requiring Java 11 when current runtime is Java 8. So that's good.
I submitted a patch to cascade that to MPC: https://git.eclipse.org/r/#/c/162754/ . So far, this patch has received no review. It's been only 5 days, but I think we're kind of in a rush for this, because if such patch doesn't make it in 2020-06, we have a risk of users breaking their installation (like it doesn't restart) when installing content via Marketplace. So it's worth bringing the topic here for anticipation.
Beyond that MPC Git repo didn't show any activity for 2 months.
So I'm wondering:
1. Is MPC effectively active?
2. Do we have guarantee MPC can produce a new release before 2020-06?
3. If MPC committers don't react, what's the most efficient escalation process?
I'm crossing fingers that my patch just falls under the radar, that this email will trigger a review, and that I'm worrying for nothing; but better be safe than sorry!
Thanks in advance
On Fri, Mar 20, 2020 at 7:34 PM Mike Wilson <Mike_Wilson@xxxxxxxxxx> wrote:
Back to the top