|
We do discuss the schedule at other meetings. It would be useful,
if we could focus these meetings on topics related to TCK and
process requirements. But that's just my opinion.
To that end, I have a list of things that, I believe we need
clarification on. These are all tasks with requirements that we
need to convey to each API committer team. I think these need to
be reviewed, probably defined further (or additional references
provided) -- and validated for completeness -- Please consider the
following. If you were asked to perform any of the tasks listed
below, do you think you would be able to complete these
satisfactorily? If yes, great! If not, what additional details
should be provided?
- Update JavaDocs and text documents in a project such
as readme files
- Update the Specification name -- using the new
name, approved
by specification committee (need a link to a document
containing all new names)
- Update all acronyms, use new acronyms, approved
by a spec committee
- Replace references to JCP process with references
to Eclipse JESP
- Update references to other specifications with
their new names (see 1.1 above)
- Generate the "Generic" specification document, using
the instructions and recommendations provided in the Steering Committee guidance.
- Including the new Specification name
- Including the approved Scope Statement text.
- Generate API JAR from the revised source-code
(revisions as needed in (1) or (2) above).
- Post this as a pre-final update to OSSRH
- Version or API JAR and all related artifacts must
be micro +1 (orig-version + 0.0.1).
- Update in pom.xml must be 0.0.1 addition to the
previously released version (Version used in Eclipse GlassFish
5.1).
- Generate Stand-alone TCK test results using the API
JAR from (3)
- If your project has a TCK process, follow it.
- Otherwise you can follow instructions suggested here,
and here.
Automation (i.e. Eclipse Jenkins) is preferred, but manual
test run results are ok.
- Save results for confirmation that JAR is
compatible and meets requirements
- Submit to Spec. committee for ballot approval
- Include Proposed Final Versions of
- Specification
- TCK
- Java Docs if applicable
- When approved
- Update all artifacts to final / released status
- Release to final locations (Maven, Eclipse
download, GitHub release) as needed
On 6/28/2019 7:20 AM, Paul Buck wrote:
As well as the review and discussion on the JESP Operations
document, can we also do a checkpoint on the schedule?
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
