Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deliver servlet-api Specification Version update for Jakarta EE 9 #286

Closed
11 tasks done
kwsutter opened this issue Jan 14, 2020 · 17 comments
Closed
11 tasks done

Deliver servlet-api Specification Version update for Jakarta EE 9 #286

kwsutter opened this issue Jan 14, 2020 · 17 comments
Labels
Epic Top level issue for tracking work wave:1

Comments

@kwsutter
Copy link

kwsutter commented Jan 14, 2020 •
edited by arjantijms

Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9

ToDo

  • Create Eclipse Release Record in your respective Jakarta Specification Project.
    Most Component Release Records will just reference the Jakarta EE 9 Platform Release Plan. But, if your Component deviates at all from the Platform Release Plan, then a description of the changes will be required in the Release Record.
    https://projects.eclipse.org/projects/ee4j.servlet/releases/5.0
  • Initiate a ballot for your Jakarta Release Record/Plan. - N/A
    Again, if your component is only doing the required minimum as defined by the Jakarta EE 9 Platform Release Plan, then no separate ballot is required. You are already approved. But, if your component deviates from the Platform Release Plan, then you will need to initiate your own ballot as defined by the Jakarta EE Specification Process.
  • Jakarta-ize your Specification document (if applicable)
    Many of the Jakarta EE components now have the source for their Specification documents. It is strongly recommended that these Specification documents are properly updated to represent Jakarta EE instead of Java EE. Some helpful instructions are documented here.
  • javax -> jakarta Spec updates
    If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
  • javax -> jakarta API updates
    Your component APIs need to move from using the javax namespace to using the jakarta namespace.
  • Release Candidate (RC) of Jakarta API in Maven Central
    A Release Candidate of your component API should be pushed to Maven Central as soon as humanly possible. This will allow other dependent components to utilize your APIs as they are updating their APIs. Multiple revisions of these Release Candidate APIs are allowed (and probably expected) during the development cycle.
  • javax -> jakarta TCK updates
    Your component TCK needs to be updated to use the jakarta namespace.
  • javax -> jakarta Compatible Implementation updates
    Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace.
  • Final Jakarta API available in Staging Repo
    When ready, your final version of the API needs to be staged to get ready for the PR review and approvals.
  • Draft Specification and Apidoc PRs ready for review
    Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots.
  • Release Review Ballot started
    Each Jakarta EE component will need to initiate a separate Release Review ballot after proper reviewing has completed. To be clear, there will not be a blanket Release Review for all of Jakarta EE 9 like we did for the Plan Review. Each component needs a separate Release Review.
@kwsutter kwsutter added this to Plan in Jakarta EE 9 Jan 14, 2020
@kwsutter kwsutter moved this from Plan to Plan Review in Jakarta EE 9 Jan 14, 2020
@gregw gregw removed Epic labels Jan 18, 2020
@kwsutter
Copy link
Author

Can I ask this team to please create and assign the following labels to this Issue? Thank you!
[Epic]
[wave:1]

I noticed that the [Epic] label has been assigned and removed... In order to help us track the progress of the overall Jakarta EE 9 release, we've asked for the Spec Projects to help out with some Issue labeling (for those Projects where I do not have committer access). Thanks for your help!

@arjantijms arjantijms added Epic Top level issue for tracking work wave:1 labels Jan 20, 2020
@kwsutter
Copy link
Author

Now that you have an RC for the API, can I ask that you post a link to the Maven artifact on the project board? https://github.com/orgs/eclipse-ee4j/projects/17#column-7346435

Thanks!

@kwsutter kwsutter moved this from Plan Review to In Progress in Jakarta EE 9 Jan 21, 2020
@pnicolucci
Copy link

pnicolucci commented Jan 22, 2020 •
edited

Removing check from Release Candidate (RC) of Jakarta API in Maven Central as I don't see an RC out on Maven Central, I only see an M1.

@kwsutter
Copy link
Author

kwsutter commented Feb 4, 2020

Now that we have adjusted the requirement for a Milestone vs RC API jar file, could we get the Servlet 5.0 M1 API mentioned via a Notecard in the Milestone/RC column of the Project Board? Thanks!

@kwsutter
Copy link
Author

I went ahead and created the Servlet 5.0 Release Record: https://projects.eclipse.org/projects/ee4j.servlet/releases/5.0

I have also updated the checklist to show that this was completed. I also marked the Release
Plan Review work item since this was covered by the overall Jakarta EE 9 Release Plan review.

@kwsutter kwsutter moved this from In Progress to Making Progress... (at least 4 of 11) in Jakarta EE 9 Mar 12, 2020
@thadumi
Copy link
Contributor

thadumi commented Apr 11, 2020

Hi, if there is nobody taking care of the specification, I'd like to update it.

@stuartwdouglas
Copy link
Contributor

Do you mean the spec document? If so I don't think anyone is working on it currently. I went through and fixed all the formatting a while ago, but did not update the text.

@arjantijms
Copy link
Contributor

Compatible implementation updated in

@arjantijms
Copy link
Contributor

TCK updated in jakartaee/platform-tck@67aca21#diff-45054851fcf26fdebe793539a039d8f4

@arjantijms arjantijms moved this from Making Progress... (at least 4 of 11) to Almost there... (at least 8 of 11) in Jakarta EE 9 Jun 7, 2020
@kwsutter
Copy link
Author

One last request for the Specifications PR to promote the Milestone deliverables for this Project. The PR is created against the Jakarta EE specifications github repo. A template is automatically used when creating PRs against this repo which should help with understanding the steps required for a successful merge. We're not looking for perfection for this Milestone. We just want the ability to promote the great work that all of the Projects are doing.

If you submit a PR, please feel free to move this Epic to the Milestone 1 Ready column in the Project Board. Thanks!

@kwsutter kwsutter moved this from Almost there... (at least 8 of 11) to Milestone 1 Ready in Jakarta EE 9 Jun 12, 2020
@kwsutter
Copy link
Author

Looking for an update on the status of the Servlet Final Specification PR. If we're going to make the Sept deliverable goal, then this Wave 1 Specification needs to be ready for final ballot by Monday, July 19. Which means that the Specification PRs should already be created and under a "mentorship" review. Can I ask what the plans are for this Specification? Thanks!

@markt-asf
Copy link
Contributor

I believe the API work is complete. There are some clarifications it would be good but not essential to include.
The specification document is still in progress. I'm currently about 50% of the way through a side-by-side comparison with the 4.0 spec doc to check the conversion process hasn't garbled the formatting, section numbering, cross-references etc.
The current issues have not yet been reviewed and there are various aspects of the POM that need to be double checked.
This is currently what I am working on.

@kwsutter kwsutter moved this from Milestone 1 Ready to Specification PRs Ready for Review in Jakarta EE 9 Jul 20, 2020
@arjantijms
Copy link
Contributor

Final Jakarta API available in Staging Repo

https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/servlet/jakarta.servlet-api/5.0.0/

@arjantijms
Copy link
Contributor

Draft Specification and Apidoc PRs ready for review

jakartaee/specifications#232

@arjantijms
Copy link
Contributor

arjantijms commented Sep 15, 2020 •
edited

@arjantijms
Copy link
Contributor

Completion steps: #366

@arjantijms
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic Top level issue for tracking work wave:1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@gregw @stuartwdouglas @arjantijms @markt-asf @kwsutter @thadumi @pnicolucci