|
|
| (10 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | # Scan and make the following changes in javadocs and all text files such as (README.md, NOTICE.md, CONTRIBUTION.md, etc) in a repository
| + | Moved [https://wiki.eclipse.org/How_to_Prepare_API_Projects_for_the_Jakarta_EE_8_Release here]. |
| − | ## Update project name as it listed on Eclipse project page (ex. [https://projects.eclipse.org/projects/ee4j.jsonb Jakarta JSON Binding])
| + | |
| − | ## Update acronyms, use new acronyms, approved by a spec committee (see guideline [https://jakarta.ee/legal/acronym_guidelines/ here]).
| + | |
| − | ## Update references to other specifications with their new names
| + | |
| − | ## Remove references to JCP process or replace them with references to JESP.
| + | |
| − | ##* Example: [https://jcp.org/en/jsr/detail?id=367 JSR-367] -> [https://projects.eclipse.org/projects/ee4j.jsonb Jakarta JSON Binding]
| + | |
| − | # Generate the "boilerplate" specification document, using the instructions and recommendations provided in the [https://docs.google.com/document/d/1EGSnr8mmNKIp3eb7odz6jpOoc3qwTISO3uzFMuvf5wc/edit Steering Committee guidance] (The document is still under Steering Committee review, but projects are free to take the recommended actions immediately).
| + | |
| − | #* Use the same spec version number as the previously released spec
| + | |
| − | # Make a staging release of API JAR from the revised source code.
| + | |
| − | #* Source code should use the new specification names and follow the acronym guidelines, and should remove any JSR references.
| + | |
| − | #* Javadocs should include the Eclipse Foundation Specification License.
| + | |
| − | #* Version in pom.xml should be increased by 0.0.1 comparing to the previously released API artifact
| + | |
| − | # Generate Stand-alone TCK test results. Use version staged on the previous step. There are some ways how to do it. Teams are free to choose any of them:
| + | |
| − | ## Create custom TCK test job
| + | |
| − | ##* Guidance is [https://www.eclipse.org/lists/ee4j-pmc/msg01985.html here].
| + | |
| − | ##* Save the test results when all tests succeed.
| + | |
| − | ## Manually run TCK by whatever means the project has used in the past. Save results when all tests succeed.
| + | |
| − | # When tests are passed submit for ballot
| + | |
| − | #* Specification Document from (2) above
| + | |
| − | #* Final TCK test bundle
| + | |
| − | #** Final version of standalone TCK bundles will be uploaded to Eclipse downloads
| + | |
| − | #* Final JavaDocs (from 3)
| + | |
| − | # When approved
| + | |
| − | #* Release staged artifacts to Maven Central
| + | |
| − | # If (5) is accomplished prior to Ballot submission deadline (currently July 15) and Eclipse has released specification text to your project -- please feel free to start to generate a more detailed Jakarta EE specification, from the contributed specification text.
| + | |
| − | | + | |
| − | [[Category:Jakarta_EE]]
| + | |
