[rest-dev] Github Issue Tracking

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

[rest-dev] Github Issue Tracking

From: "Markus Karg" <markus@xxxxxxxxxxxxxxx>
Date: Sat, 27 Jan 2024 10:08:27 +0100
Delivered-to: rest-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/rest-dev/>
List-help: <mailto:rest-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/rest-dev>, <mailto:rest-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/rest-dev>, <mailto:rest-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AdpRAGOnxtzpv/d9Sr2uDkciJVH/KQ==

To have a better overview over all the new issues opened regarding 3.2, @Context replacement, etc. I would propose that we let us help from Github:

* Anything related to replacing @Context etc. (unrelated to any specific target version) should be labelled by "@Context" etc.

* Anything planned for inclusion in 3.2 should be moved into the 3.2 project. This includes moving issues from 4.0 to 3.2 project.

* …

WDYT?

-Markus

Follow-Ups:
- Re: [rest-dev] Github Issue Tracking
  - From: Jim Krueger

Prev by Date: Re: [rest-dev] [External] : Start version 3.2
Next by Date: Re: [rest-dev] Github Issue Tracking
Previous by thread: [rest-dev] release-3.2 branch created
Next by thread: Re: [rest-dev] Github Issue Tracking
Index(es):
- Date
- Thread

Back to the top