Re: [m2e-dev] Release for SimRel 2022-06

[Hannes Wellmann <wellmann.hannes1@xxxxxxx>]

I agree with Christoph, that we should really remove all deprecated code before the release.

I cannot estimate at the moment how much work that is? If it just has to be deleted, May 20th is possible, if we have to find replacements it could be difficult to be ready then.

 

One issue I have at the moment with the current snapshot is that many Connectors and Oomph does not work with M2E 2.0 because they were good citizens and specified a proper version range on M2E.

Therefore I cannot test the M2E snapshot in my daily work. But this is likely a chicken-egg problem here. Maybe if we knew definitely what API will be removed we could ask Oomph and others to relax the version range to 3.0 already?

 

The other changes would indeed nice to have but are not blockers for the next release and I sadly don't have the time to work on them a.t.m..

 

Gesendet: Dienstag, 03. Mai 2022 um 15:56 Uhr
Von: "Christoph Läubrich" <laeubi@xxxxxxxxxxxxxx>
An: m2e-dev@xxxxxxxxxxx
Betreff: Re: [m2e-dev] Release for SimRel 2022-06

I don't think we are ready for 2.0 release as a lot of deprecated code
is not yet removed and that was the main goal for 2.0 ...

Am 03.05.22 um 14:52 schrieb Mickael Istria:
> Hi all,
>
> We want to contribute newer m2e into SimRel 2022-06. As there are many
> API changes, we should do a release ASAP to leave time to others to react.
> The currently remaining items are
> https://github.com/eclipse-m2e/m2e-core/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0
> <https://github.com/eclipse-m2e/m2e-core/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0>
> ; I don't see any that is a blocker before we can release. Most of them
> are "nice to have" and some of them are clearly too complex to hope a
> resolution before next month.
>
> So what would be a good date for a release? I suggest around May 20th.
> What do you think?
> --
> Mickael Istria
> Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
> Developers <https://developers.redhat.com/>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev