As is my tradition, I've tried to pick the releases that
best match my understanding of what bits you're actually
including in the release.
Please have a look and validate that I've gotten your
project(s) right. Let me know (via this list) if I've messed
Some things that I've noticed.
Eclipse DLTK shows a version 6.2 in the aggrcon
file, but there's no corresponding release record. There's
only a handful of updates, so I created a "6.2" release
record and marked it as a "service release". If it's
actually a minor release that provides more than bug fixes,
contact EMO ASAP to request an expedited progress review
(AFAICT all third party intellectual property is properly
accounted for, so a progress review should be relatively
The aggrcon file for the Eclipse Extended Editing
Framework shows a version range of [1.5.0,1.6.0)
which, AFAICT is pulling version 1.5.1 into the builds. That
release came out in 2015. The project has had several
releases since. It seems... odd... to have a release this
old when newer ones are available.
The Eclipse Mylyn project has been collapsed and
moved under the Eclipse Tools TLP. Eclipse Mylyn dropped out
of the simultaneous release a few iterations ago, but
Eclipse Mylyn Docs has stuck around.
As part of collapsing the Eclipse Mylyn subprojects into
the parent, the assets of the Eclipse Mylyn Docs project
were absorbed into the parent and Eclipse Mylyn Docs now
effectively ceases to exist (the project is still marked as
being active, but we'll take care of that shortly).
The net is that you'll notice that Eclipse Mylyn Docs is
gone and Eclipse Mylyn is back. I created a release record
in Eclipse Mylyn titled "Docs 3.0.42" to reflect the content
that the aggrcon file shows as included in the simultaneous
To be clear... to the best of my knowledge, Eclipse Mylyn
is not back yet. The changes shown in the project list are
I trust that somebody will let me know if I've made a
horrible, horrible mistake.
Director of Open Source Projects
| Eclipse Foundation
My working day may not be
your working day! Please don’t feel
obliged to read or reply to this
e-mail outside of your normal