Re: [jakarta.ee-spec.committee] Fw: Re: [jakarta.ee-spec] BALLOT: Approv

["Kevin Sutter" <sutter@xxxxxxxxxx>]

I thought that we
(mere mortals) were supposed to commit to "src" and the web team
will take care of merging into "master"...  Is there anyway
to open up "src" for the spec committee?  Thanks!

Otherwise, why
do we have "src" and "master"?  If we don't have
write access, then we can only do PRs and let the other review it and merge
into "master".  Seems kind of confusing...

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Ivar
Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
To:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       02/20/2020
16:01
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec.committee] Fw: Re: [jakarta.ee-spec] BALLOT: Approval
to release Jakarta EE "javase" specifications
Sent
by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

Hi Kevin,

Currently, it is the members of the web
team at Eclipse that are committers to the web page. The PRs are normally
processed within 24 hours, but if it takes longer we can probably request
for someone in the Specification Committee to be added to the committer
list.

Ivar

On Thu, Feb 20, 2020 at 4:55 PM Kevin
Sutter <sutter@xxxxxxxxxx>
wrote:
I just noticed
that I don't have write access to this repo?  https://github.com/jakartaee/jakarta.ee

Do I have to open a bug report to get this resolved?  How were the
list of committers determined?

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        "Kevin
Sutter" <sutter@xxxxxxxxxx>
To:        Bill
Shannon <bill.shannon@xxxxxxxxxx>
Cc:        Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        02/20/2020
14:26
Subject:        [EXTERNAL]
Re: [jakarta.ee-spec.committee] Fw: Re: [jakarta.ee-spec] BALLOT: Approval
to release Jakarta EE "javase" specifications
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

Here's the PR for the updated Operations Guide:  https://github.com/jakartaee/jakarta.ee/pull/641.
 Looking for a review/approval by anyone on the Spec Committee. 
Thanks!

I also found an approved PR
that had deleted the old version of the Ops Guide,
but it hadn't been merged yet.  It is now...  :-)

I am still on the hook to document my findings on duplicate information
or lack of information (like a more elaborate finalization checklist).

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        Kevin
Sutter/Rochester/IBM
To:        Bill
Shannon <bill.shannon@xxxxxxxxxx>
Cc:        Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        02/20/2020
13:23
Subject:        Re:
[EXTERNAL] Re: [jakarta.ee-spec.committee] Fw: Re: [jakarta.ee-spec] BALLOT:
Approval to release Jakarta EE "javase" specifications

---

Thanks, Bill, for letting me know about the markdown version...  I
was updating the wrong one...  I will submit a separate PR to mark
this file (whole repo?) as legacy and point at the jakarta.eerepo instead.

Not sure about a more elaborate finalization checklist...  What I
am finding is that we have similar information posted in multiple places
for this Spec Release process...  I will at least create an Issue
with what I have found so that can consolidate.

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter




From:        Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:        Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>,
Kevin Sutter <sutter@xxxxxxxxxx>
Date:        02/20/2020
12:48
Subject:        [EXTERNAL]
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 guidewas 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.eerepo 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.




_______________________________________________
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


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Eclipse
Foundation:
The Platform for Open Innovation and Collaboration_______________________________________________
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