I would be against this proposal.
I would rather (once again) raise the awareness of the active committers about "eating your own dog food" and use the milestone week to actually try the latest greatest nightly builds.
We have too many regressions that only found by users after release, so having a week where people hold on for a moment with hacking and try to test the product should help our users.
This is especially important for M1 because many "mass changes" that silently break untested code happen usually there.
Спасение утопающих - дело рук самих утопающих
Gesendet: Donnerstag, 28. April 2022 um 11:59 Uhr
Von: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx>
An: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
Betreff: [eclipse-dev] Lightweight M1 for September release
We had the lightweight M2 release process for a couple of years already and there are no problems that came out of M2 builds . Thus I would like to propose the following:
Use the same lightweight release process for M1 starting with the next release cycle.
This means no milestone week with all the associated limitations coming from it.
If that process is good enough for M2 I see no reason to have a heavier one for earlier milestone release.
P.S. Let's keep this discussion about the M1 release process and discuss further process enhancement if/when we do the change for M1. Step-by-step approach is always best and allows some progress to be made rather than striving for the next big thing/change.
Red Hat Eclipse Team
_______________________________________________ eclipse-dev mailing list eclipse-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev