Hi Wayne,
the versions for the soa-bpel.aggrecon and the mdt-bpmn2.aggrecon are
not as I expected them.
I have submitted my changes to gerrit under the following commit address:
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/167721
The new versions for these parts are:
*mdt-bpmn2.aggrecon from 1.5.0 -> 1.5.1*
<repositories
location="https://download.eclipse.org/modeling/mdt/bpmn2/updates/2020-09/1.5.1">
<features name="org.eclipse.bpmn2.feature.feature.group"
versionRange="1.5.1">
<categories
href="simrel.aggr#//@customCategories[identifier='SOA%20Development']"/>
</features>
</repositories>
*soa-bpel.aggrecon from 1.1.2 -> 1.1.3*
<repositories
location="https://download.eclipse.org/bpel/updates/2020-09/1.1.3">
<features name="org.eclipse.bpel.common.feature.feature.group"
versionRange="1.1.3">
<categories
href="simrel.aggr#//@customCategories[identifier='SOA%20Development']"/>
</features>
<features name="org.eclipse.bpel.feature.feature.group"
versionRange="1.1.3">
<categories
href="simrel.aggr#//@customCategories[identifier='SOA%20Development']"/>
</features>
<features
name="org.eclipse.bpel.apache.ode.runtime.feature.feature.group"
versionRange="1.1.3">
<categories
href="simrel.aggr#//@customCategories[identifier='SOA%20Development']"/>
</features>
</repositories>
It looks like this changes have not made it into the simrel.
You know I am new in this role and I wonder what I have done wrong? I
submitted my changes to gerrit at the 2020-08-14 23:25:10 . As my
commits looked fine I expected this changes will be merged. But now I
see there are merge conflicts. I am pretty sure that I have pulled the
org.eclipse.simrel.build project imidiately before I pushed my changes
to gerrit.
Can you help me with this issue?
Best regards
Ralph
On 27.08.20 20:50, Wayne Beaton wrote:
I've created the tracking page for 2020-09
<https://projects.eclipse.org/releases/2020-09>. Please have a look to
ensure that I've correctly recorded your project's participation
correctly.
In particular, please make sure that I have the version right. If I've
made a mistake... please first make sure that you've created a release
record for the right version and then let me know to update the
tracking page to point to that version.
If you are contributing a new major or minor release and have not
engaged in a release review since September 16/2019, then you need to
submit your IP Log and connect with EMO ASAP to initiate the release
review process. Note that you only need to submit your IP Log for
review if you are required to engage in a release review. There's more
information in the handbook
<https://www.eclipse.org/projects/handbook/#release>.
Based on messages on this list, both Eclipse Corrosion, Eclipse
EMFStore, and Eclipse Tools for Cloud Foundry (CFT) have dropped out,
so they've been removed from the list.
*AFAICT, the corrosion.aggrcon file still exists and is not
disabled.* Also, since CFT has dropped out, its aggrcon file should
also be removed (not just disabled). Can somebody take care of that,
please?
Thanks for all your efforts.
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Join us at our virtual event: EclipseCon 2020
<https://www.eclipsecon.org/2020>- October 20-22
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
*Imixs Software Solutions GmbH*
*Web:* www.imixs.com <http://www.imixs.com> *Phone:* +49 (0)89-452136 16
*Office:* Agnes-Pockels-Bogen 1, 80992 München
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsführer: Gaby Heinle u. Ralph Soika
*Imixs* is an open source company, read more: www.imixs.org
<http://www.imixs.org>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev