[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Release Planning
|
Why then not simply doing an automatic release after each change?
> people will have to install 2.x soon anyway.
and complain about any of the m2e plugins that break thanks to the
eclipse rule not setting an upper bound for dependencies...
Am 08.02.22 um 11:30 schrieb Mickael Istria:
This proposal is more complicated and not more valuable than the current
state: any committer can release at any time assuming minimal quality
(running test suite, compatible with last Eclipse IDE release) is
verified. Some committers who are in need of a release and ready to
invest in it should be able to release immediately and not be slown down
in doing so by some other committers who planned more complex and longer
work.
The very important thing is for the project to release often, to deliver
more value and get more feedback and a more active community. Anything
that's about reducing the frequency of release or the agility in
performing them is to be perceived as harmful for the project.
The particularity these days is that it's supposed to be the last one of
1.x, so people will have to move to 2.x to get further changes, But
realistically, as m2e most likely won't support any 1.x at all after
that, it doesn't make a difference: people will have to install 2.x soon
anyway.
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
