Wayne,
If you look at the Object Teams commit history you'll see it's regularly
disabled and then enabled. This is because its patch features must be
carefully coordinated with the features JDT contributes to the train.
Given that Stephen Herrman is responsible, I don't expect there is any
problem here; it being disabled in a transient situation.
Lua/LDT got disabled 4 months ago as a side effect of a DLTK
contribution. So I believe it was absent in 2019-12 too. New content
was last contributed more than a year ago. I would assume this project
is AWOL and that no one actually cares.
I would not expect any response from JWT. I announced its removal to
this list:
https://www.eclipse.org/lists/cross-project-issues-dev/msg17419.html
The project is dead.
Regards,
Ed
On 25.02.2020 16:24, Wayne Beaton wrote:
Greetings folks.
I've created the 2020-03 Participation Page
<https://projects.eclipse.org/releases/2020-03> using the information
that I have available. Please have a look to make sure that I've
gotten it right.
As far as I am aware, the only project that has formally dropped out
is EMF Diff/Merge. There are three other projects with disabled
aggrcon files: Eclipse ObjectTeams, Eclipse Lua Development Tools, and
Eclipse JWT. With only one final milestone to go, it feels very wrong
to have these disabled at this stage. Project teams please engage to
get these contributions sorted out.
I did try to confirm many (but not all) of the version numbers listed
on the participation page with version information in the aggrcon
files (in those cases where the information was apparent). If I've
gotten the version wrong, please first make sure that you've created a
release record with the correct version number and date and then let
me know so that I can fix the reference. Note that the release records
are connected by reference, so if you change the release record that
is already linked from the participation page, that change will be
reflected.
I noted that the Eclipse RCP Testing Tool 2.5.1 release (which is the
version referenced in the aggrcon file) had the wrong release date, so
I changed it to 2020-03-18. Let me know if I've made a horrible,
horrible mistake.
Note that, if you are contributing a new release to 2020-03, you only
need to engage in a release review if you have not already engaged in
a successful release review in twelve months ending on 2020-03-18.
Note also that you only need to submit your IP Log for review when you
engage in a release review (so if you've done a successful release
review since March 18/2019, you do not need to submit your IP Log for
review). You are, however, responsible for making sure that the
intellectual property included in and referenced by your project has
been properly vetted. If you're not sure, you can always submit your
IP Log and I'll have a look.
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
