Jakarta SOAP with Attachments 1.4

[lukasj]

Signed-off-by: Lukas Jungmann lukas.jungmann@oracle.com

PR#1:

• A directory in the form wombat/x.y where x.y is the release major.minor version, and the directory contains the following.
• Specification PDF in the form of wombat_x.y.pdf
• Specification HTML in the form of wombat_x.y.html
• A specification page named _index.md following the template at:
  https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md
• For a Release Review, a summary that a Compatible Implementation
  is complete, passes the TCK, and that the TCK includes sufficient
  coverage of the specification. The TCK users guide MUST include
  the instructions to run the compatible implementations used to
  validate the release. Instructions MAY be by reference.
• The URL of the OSSRH staging repository for the api, javadoc:
  https://oss.sonatype.org/content/repositories/staging/jakarta/xml/soap/jakarta.xml.soap-api/1.4.2/
• The URL of the staging directory on downloads.eclipse.org for the proposed EFTL TCK binary:
  http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/promoted/eclipse-soap-tck-1.4.0.zip
• The URL of the compatibility certification request issue:
  Compatibility certification request for Jakarta SOAP with Attachments implementation saaj-api#49, Compatibility certification request for Eclipse Metro 2.4.3 saaj-api#51

Include the following in PR#2:

• Specification JavaDoc in the wombat/x.y/apidocs directory.

[netlify]

Deploy preview for jakartaee-specifications ready!

Built with commit d0fab1a

https://deploy-preview-46--jakartaee-specifications.netlify.com

[lukasj]

this one should be ready too; the only thing is that the compatible implementation has no name, so I used "Jakarta SOAP with Attachments Implementation"

[kwsutter]

Just putting a "hold" tag on this issue since it hasn't been decided whether the jax-ws specs will be part of Jakarta EE 9 or not...

[bshannon]

Just putting a "hold" tag on this issue since it hasn't been decided whether the jax-ws specs will be part of Jakarta EE 9 or not...

We can approve this spec whether it's included in Jakarta EE 9 or not, right?
Approving this (and other related) spec allows it to be used in standalone
implementations and Jakarta EE implementations independently of the JCP.

[kwsutter]

LGTM

[lukasj]

TODOs: upload refreshed binaries, fix TCK URL

[lukasj]

binaries were refreshed

[kwsutter]

Approve, but the names of the Specs should be updated to be consistent with the rest of Jakarta EE.

[kwsutter]

• The designated specification committee representative adds this final checklist to the main PR.
• The specification committee representative merges the specification and apidocs PRs.
• The designated specification committee representative calculates the staged EFTL TCK signature and promotes it to the committee download area
  using the https://ci.eclipse.org/jakartaee-spec-committee/job/promote-release/ job.
• The specification project member who created the staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
• The EMO updates the specification page with the ballot results.
  This list goes on the committed spec index page.
• The specification project team should go through the merged spec website page to verify all the links are valid.
• The specification project team should approve the compatibility request.
• The compatible implementation project/vendor MUST send an email tck@eclipse.org for approval of the compatible implementation for trademark usage.
• The specification project team should merge any final release branch as appropriate for the branch management for the project.

[lukasj]

@kwsutter unchecked items were done

[kwsutter]

Thanks!