Re: [m2e-dev] Starting a 2.0 with breaking changes soon?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [m2e-dev] Starting a 2.0 with breaking changes soon?

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Wed, 2 Feb 2022 16:40:59 +0100
Delivered-to: m2e-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/m2e-dev/>
List-help: <mailto:m2e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=unsubscribe>

On Tue, Feb 1, 2022 at 7:05 AM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx> wrote:

I think the best would be if we goo through the issues and assign a
milestone to them, then it would be clear what is a candidate for this
release and for the 2.0.0

I think we should just assume everything is for 2.0, and make a few exceptions of the task that are currently close to completion and seem extremely valuable to ship ASAP. Those can be marked to a 1.7 milestone.

But is there any of such PRs left?

Follow-Ups:
- Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
  - From: Christoph Läubrich

References:
- [m2e-dev] Starting a 2.0 with breaking changes soon?
  - From: Mickael Istria
- Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
  - From: Mickael Istria
- Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
  - From: Hannes Wellmann
- Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
  - From: Christoph Läubrich

Prev by Date: Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
Next by Date: Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
Previous by thread: Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
Next by thread: Re: [m2e-dev] Starting a 2.0 with breaking changes soon?
Index(es):
- Date
- Thread

Breadcrumbs