jakartaee / jakartaee/security

Security 5.0 Milestone 2

Open
#358 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
66
Forks
43
PR merge metrics
No merged PRs in 30d

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**
- [ ] Service release branch created for N-1 release
- [ ] New / master / main branch up-to-date with service release updates from previous version
- [ ] If not done, move from master branch to main.

**Code updates**
- [ ] 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
- [ ] 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
- not applicable

**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

Open the contributing guide

Research direction

Start by reviewing the linked dashboard and the referenced platform issues, then work through the unchecked API, specification, branch, OSSRH, TCK, and Jenkins checklist items. Done means all applicable Milestone 1 actions are completed and their status is reflected in the issue or dashboard.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd, release, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.