[jakarta.ee-spec.committee] Last steps in Spec. approval?

[Ed Bratt <ed.bratt@xxxxxxxxxx>]

I believe the Dependency Injection Spec. is ready to go (PR 221). (it's probably been ready to go for several days now, but I've been looking at other things :-( ). The TCK needs to be moved to the final download location and the SHA and PUB key files need to be created.

How are these created?

As the mentor, do something to create these? Do I click the "Merge" button on the PR? Who updates those final three links (TCK d/l, SHA255 file, and Pub. Key file)? I can predict the links, so I conceivably could just request the changes -- then, who pushes the button to promote the TCK and generate the actual files?

the state location for the TCK is: https://download.eclipse.org/ee4j/cdi/inject/2.0/jakarta.inject-tck-2.0.1-bin.zip

From that, I think the finals are:

• d/l: https://download.eclipse.org/jakartaee/dependency-injection/2.0/jakarta.inject-tck-2.0.1-bin.zip
• sig: https://download.eclipse.org/jakartaee/dependency-injection/2.0/jakarta.inject-tck-2.0.1-bin.zip.sig
  
• SHA-256: https://download.eclipse.org/jakartaee/dependency-injection/2.0/jakarta.inject-tck-2.0.1-bin.zip.sha256
• pub: https://raw.githubusercontent.com/jakartaee/specification-committee/master/jakartaee-spec-committee.pub

Thanks,

-- Ed