[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Version/Release/Compatibility Policy
|
Hi Gunnar,
> has a significant user base
That's great to hear!
> Quite a a significant amount of these users are enterprise customers
> which do expect some kind of stability, compatibility and
announcements around upcoming breakages
Everyone is encouraged to participate and help to fulfill these
"expectations" see:
https://github.com/eclipse-m2e/m2e-core/blob/master/CONTRIBUTING.md
so anyone requiring enterprise-support can either:
1) directly contribute
2) pay someone to contribute on there behalf
Its all open source and even help to do project management, bug triage,
testing of snapshots are all more than welcome...
> It's a good practice for mature, stable Eclipse projects, with a
> significant user base, to create and publish a
version/release/backwards compatibility.
As mentioned in your issue created, there is always older releases
available in case of any (unexpected) problem here:
https://download.eclipse.org/technology/m2e/releases/
> Eclipse Git integration generally
> tries to support the last N-2 Eclipse versions with their releases
This is not a goal of m2eclipse as no one of the active committer nor
contributor can (or want to) afford this and it limit us delivering new
features or improve existing ones.
> Appreciate your support
Simply use https://download.eclipse.org/technology/m2e/releases/2.0.1/
for now or propose a PR and we probably can do another release soon that
includes this fix.
Am 31.08.22 um 19:49 schrieb Gunnar Wagenknecht:
Greetings M2E Committers,
I'd like to make you aware that M2E has a significant user base outside
of the committer bubble. Quite a a significant amount of these users are
enterprise customers, which do expect some kind of stability,
compatibility and announcements around upcoming breakages.
Lately, an issue that I ran into myself within the organization I work
with is this:
https://github.com/eclipse-m2e/m2e-core/issues/887
<https://github.com/eclipse-m2e/m2e-core/issues/887>
The M2E `/latest` update site got broken because it suddenly depends non
*none official*, *none released* artifacts of other Eclipse projects.
This is not only problematic from a customer/user point of view, it's
also problematic from an Eclipse Development Process and IP process
point of view. As a member of the Technology PMC, the latter is more
concerning for me.
It's a good practice for mature, stable Eclipse projects, with a
significant user base, to create and publish a version/release/backwards
compatibility. As an example, the Eclipse Git integration generally
tries to support the last N-2 Eclipse versions with their releases. I do
consider M2E as important as EGit and thus, my recommendation is to
implement something similar for M2E.
I think that at a very minimum, the `/latest` update site should point
to a release, which does not depend on unreleased artifacts.
Appreciate your support and respect of the EDP and best practices.
.Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx <mailto:gunnar@xxxxxxxxxxxxxxx>, http://guw.io/
<http://guw.io/>
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
