You should give it the +2 yourself and then it the submit
button.Â I assume you have authorization to do that and if not,
you should get it.
I did it for you this time, in case you are not already
On 26.08.2019 10:46, Matthias Wienand
I updated the GEF contribution for 2019-09 Simrel M3
to 5.2.0, which is available for review here:
Thanks in advance for the review :-)
Telefon: +49 231 9860 202
Telefax: +49 231 9860 211
Mobil: Â +49 176 248 950 82
Am Brambusch 15-24
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.),ÂWolfgang Neuhaus,
Aufsichtsrat: Prof. Dr. Burkhard IgelÂ(Vors.),
Michael Neuhaus, JenniferÂFiorentino
To change your delivery options,
retrieve your password, or unsubscribe from this list,
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev as correctly stated on the
participation page, Eclipse Marketplace Client will
participate in the release. But our version number
will be 1.8.0 instead of 1.7.7. We had updated the
aggrcon file and created a corresponding release
record a while ago. Did we miss something or was
that just not updated on the participation page?
updated theÂ2019-09 participation pageÂ
based on the
information available. A great many projects (26 at
this point in time) haveÂnotÂ
indicated that they are participating in the
release. The instructions areÂhere
opt-in deadline was August 9.
I have updated theÂparticipation pageÂ
information that I have available. Let me know
if I've got anything wrong.
Per the Simultaneous ReleaseÂparticipation rules
every participating project needs to signal
their continued participation by making a
change (any change) to the project's aggrcon
file. If your contribution will be a new
release of your content, you must also create
a release record. The date on the release
record should be the date of the release
(2019-09-18); when I add your project to the
list, I pick the release record with a date on
or before the date of the Simultaneous
Note that changes made the Eclipse
Development Process require a release review
(and IP Log review) only if the release is
major or minor and your project has not done a
release review in the past year. As always,
service releases do not require a review. Do
note, however, that you are still required to
have all of your intellectual property fully
vetted and cleared by the IP Team before it
can be included in any release (regardless of
whether or not you engage in a review).
I'll check again and update the
participation list accordingly next week. The
opt-in deadline is M2, so after tomorrow...
Thanks for your attention.
Don't panic yet. I
start to build this list in earnest around
the M2 mark.
I'll make sure that
Eclipse Web Tools makes the list.
Open Source Projects |ÂEclipse
of Open Source Projects |ÂEclipse Foundation,
Director of Open Source
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit