Activation 2.2 Milestone 1
- Dominant language
- Java
- Stars
- 43
- Forks
- 34
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
For Milestone 1, if possible it would be ideal to complete the following minimum actions. Milestone 1 work should be completed by October 15 including API, Javadoc, and specification doc artifacts being available. Ideally there would also be a Milestone version of the TCK as well. Status for the Milestone 1 issues will be tracked using [this dashboard](https://github.com/orgs/jakartaee/projects/20/views/1).
**GitHub updates**
- [x] Service release branch created for N-1 release
- [x] New / master / main branch up-to-date with service release updates from previous version
- [x] If not done, move from master branch to main.
**Code updates**
- [x] Version update to the new version number including updating Export and Import versions in API jar’s MANIFEST.MF and Specification document
- [x] TCK brought over from platform repo if appropriate (do not delete from platform-tck repo until ratified)
- not applicable
- [ ] Remove all tests from exclude list
- [x] Updates for the SEO change in the specification document as outlined in https://github.com/jakartaee/platform/issues/1108
- [x] Do changes necessary to remove references to Java SecurityManager from the spec and API as outlined in https://github.com/jakartaee/platform/issues/1018
**CI updates**
- [ ] OSSRH updates
- [ ] TCK running with EE 11 ratifying implementation with Java 21 (tests could be failing due to new tests added / excluded tests no longer removed) and any other LTS versions supported by your new version. Bonus points for Java 25 running.
- [ ] Jenkins job created for the new version for API, Javadoc, spec and TCK
- [ ] Make sure service stream Jenkins jobs are working for API and TCK
Contributor guide
Research direction
Start with the unchecked items in this issue and the linked project dashboard, especially OSSRH updates, EE 11 TCK runs, Jenkins jobs, and service-stream jobs. Review the API, Javadoc, specification, and TCK release artifacts to determine which milestone requirements remain. Done means the remaining release, CI, and validation actions are completed for the new version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- ci-cd, documentation, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100