Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Lightweight M1 for September release

I think we need to examine how many or few issues/regressions were discovered in M1 milestone week instead of looking at how smoothly M2 went.  Major refactoring/cleanups and major changes (at least in JDT)
are often rescheduled to the next release's M1.  The reason is to have more testing and more time to discover any regressions.  If there is no official milestone week for M1 or M2, that means
it mostly falls to M3.  I'm not sure if our M1 and M2 milestones get much testing from our users.

-- Jeff J.

On Thu, Apr 28, 2022 at 5:59 AM Aleksandar Kurtakov <akurtako@xxxxxxxxxx> wrote:
Hey everyone,
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.

Aleksandar Kurtakov
Red Hat Eclipse Team
eclipse-dev mailing list
To unsubscribe from this list, visit

Back to the top