[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Fw: Re: [jakarta.ee-spec] BALLOT: Approval to release Jakarta EE "javase" specifications
|
Kevin Sutter wrote on 2/20/20 9:53 AM:
- For the
most part,
the operations
guide was
quite accurate. I have made a few updates and will be
creating a
PR shortly.
Note that the
operations
guide is now a
Markdown
file in the jakarta.ee repo and updates need to be made
there. The version in our repo should be removed, or replaced with
a pointer to the official version.
The one item
I
have question on is the releasing of the staged artifacts to
Maven Central.
The ops guide says this:
- When
the ballot
request PRs are approved, release staged artifacts to
Maven Central. Advice
on this can be found MavenReleaseScript.
This pointer
is
to a script that could be used by a developer to release the
staged artifacts
for a given project. Questions:
- Whose
responsibility
is it to release these artifacts to Maven Central? I would
think
the Specification Project. But, the instructions might
imply it's
up to the Specification Committee. I don't think I have
access or
ability to release the artifacts for these projects. I'd
like to
clarify the ops guide.
It has to be the specification project team.
- We may
be in a
strange limbo state since it looks like all of the JavaSE
PRs used the
old nexus sonatype for staging. Is this still available for
doing
the releasing to Maven Central? Or, do these artifacts need
to be
re-staged again to the jakartaee instance and then released?
For Activation I'm in the process of restaging and then pushing. I
don't know how easy that will be for the other APIs.
