We have many packages
that work and got a +1. We should not put more work on them to retest everything
after the respin.
As far as I understand
the problem, simply telling the Mylyn (and other projects broken by JAXB)
users to use Java 8 instead of Java 11 should do the trick for now. That
information should be placed on the 2018-12 landing page and spread via
Merks <ed.merks@xxxxxxxxx> To:
[eclipse.org-planning-council] 2018-12 Respin? Sent
My sense is that while this is a super annoying problem, we should not
assume that everyone necessary is available last minute right before the
holiday season to deal with respinning and retesting along with a delayed release. It's extremely bad timing for this time of
This post on the forum suggests the problem is more wide spread than has
currently been identified:
As such, I'm doubtful a respin will catch all the problems, and I'd be
concerned that we replace this problem with a different set of problems.
On 17.12.2018 17:45, Frederic Gurr wrote: > Dear Planning Council members, > > ICYMI, as reported in > https://www.eclipse.org/lists/cross-project-issues-dev/msg16288.htmlby > Holger Voorman, the 2018-12 RC2 "Eclipse IDE for Java Developers"
logs > errors, breaks bug/enhancement reporting and task search. > > Please decide if this justifies a last minute respin. Since time is
in > short supply, this needs to be decided today, if we don't want to
risk > delaying the release. > > Side note: I'm wondering, why theses issues were not found during
the > EPP tests. > > > Regards, > > Fred > > _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxx https://www.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.