jakartaee / jakartaee/platform

Define how the independent release of profiles should work

Open
#332 3 comments 0 reactions 0 assignees View on GitHub
jea-linked
Dominant language
No language data
Stars
230
Forks
77
Avg merge
8d 5h
Merged PRs (30d)
1

Description

**Is your feature request related to a problem? Please describe.**
We want to be able to release platform specifications on independent release schedules. How should versioning of the platform specifications be done such that this makes sense?

**Describe the solution you'd like**
There should be some major.minor versioning scheme as well as public review releases to increase the pace at which profiles are released and made publicly available.

**Describe alternatives you've considered**
None, this is a new behavior for EE.

**Additional context**
[JEP 322: Time-Based Release Versioning](http://openjdk.java.net/jeps/322)

[AB#77](https://dev.azure.com/jakarta-ee-azdo/7cf9a9d3-9854-41e0-9a66-99506a9ed874/_workitems/edit/77)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing JEP 322 and the linked AB#77 work item to understand the proposed release model. Define how independent platform-specification versioning, major.minor versions, and public review releases should work; completion would require an agreed release and versioning approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.