Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Additional Agenda topic for our working call today
I would say for our first meeting we won’t make it through the JESP, so we probably need to be more focused on Jakarta EE 8 issues in both meetings until we have confidence that Jakarta EE 8 is making it out the door on time.

On Jun 28, 2019, at 9:48 AM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

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?

  1. Update JavaDocs and text documents in a project such as readme files
    1. Update the Specification name -- using the new name, approved by specification committee (need a link to a document containing all new names)
    2. Update all acronyms, use new acronyms, approved by a spec committee
    3. Replace references to JCP process with references to Eclipse JESP
    4. Update references to other specifications with their new names (see 1.1 above)
  2. Generate the "Generic" specification document, using the instructions and recommendations provided in the Steering Committee guidance.
    1. Including the new Specification name
    2. Including the approved Scope Statement text.
  3. Generate API JAR from the revised source-code (revisions as needed in (1) or (2) above).
    1. Post this as a pre-final update to OSSRH
    2. Version or API JAR and all related artifacts must be micro +1 (orig-version + 0.0.1).
    3. Update in pom.xml must be 0.0.1 addition to the previously released version (Version used in Eclipse GlassFish 5.1).
  4. Generate Stand-alone TCK test results using the API JAR from (3)
    1. If your project has a TCK process, follow it.
      1. Otherwise you can follow instructions suggested here, and here. Automation (i.e. Eclipse Jenkins) is preferred, but manual test run results are ok.
    2. Save results for confirmation that JAR is compatible and meets requirements
  5. Submit to Spec. committee for ballot approval
    1. Include Proposed Final Versions of
      1. Specification
      2. TCK
      3. Java Docs if applicable
  6. When approved
    1. Update all artifacts to final / released status
    2. 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?


Thanks ... Paul


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

Back to the top