Re: [jakarta.ee-spec.committee] Initiate a ballot for JAF 2.0 Release Pl

["Kevin Sutter" <sutter@xxxxxxxxxx>]

I've been using April
1.  Sounded appropriate to me...  :-)  As you said, we can
adjust it as needed.


---------------------------------------------------
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:
       Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To:
       Kevin
Sutter <sutter@xxxxxxxxxx>
Cc:
       EMO
EMO <emo@xxxxxxxxxxxxxxxxxxxxxx>, Bill Shannon <bill.shannon@xxxxxxxxxx>,
Jakarta EE Specification Committee Discussions <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       02/18/2020
16:38
Subject:
       [EXTERNAL]
Re: Initiate a ballot for JAF 2.0 Release Plan?

---

I shared this privately with Bill, but
figured that I should bring it to the group to make sure that we all understand
the intent of a release record.

The release date doesn't make sense to
me.

The release
record is literally the record
that describes the release. At this point in time, it serves to inform
the community of the future release. Following the release date, it serves
as a record of the release. 

A release record contains the plan for
the release. The release date, which can be thought of as part of the plan,
is the date that the release will be pushed live. In this case, my expectation
is that the release date is sometime much later in the year (September
something?)

At this point in a release cycle, close
counts. The release date can be changed.

Does this make sense?

What is a reasonable best-guess release
date?

Wayne

On Tue, Feb 18, 2020 at 5:26 PM Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
It literally just got to the top of my
list. Sorry, some competing priorities got ahead of this. I'll put it into
the next review slot which ends on March 4.

Wayne

On Tue, Feb 18, 2020 at 5:24 PM Kevin
Sutter <sutter@xxxxxxxxxx>
wrote:
Did this get initiated,
Wayne?  I don't believe I've seen it come across my inbox yet...


---------------------------------------------------
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:        EMO
EMO <emo@xxxxxxxxxxxxxxxxxxxxxx>
To:        Kevin
Sutter <sutter@xxxxxxxxxx>
Cc:        Bill
Shannon <bill.shannon@xxxxxxxxxx>,
Jakarta EE Specification Committee Discussions <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        02/13/2020
22:51
Subject:        [EXTERNAL]
Re: Initiate a ballot for JAF 2.0 Release Plan?
Sent by:        wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx

---

Sorry for the delay, Kevin. I'll send it out tomorrow.

Wayne

On Wed, Feb 12, 2020 at 9:50 AM Kevin Sutter <sutter@xxxxxxxxxx>
wrote:
Hi EMO,
Based on last week's Spec Committee call, can we initiate a ballot for
the JAF 2.0 Release Plan?

https://docs.google.com/document/d/1wulckg85DQPGy7vGVlsWhw4H041q-ju5RD-HoYaoqMw/edit#

• I think the JAF 2.0 Release Planis ready for ballot.  [KWS]
  • Agreed ready for ballot

https://projects.eclipse.org/projects/ee4j.jaf/releases/2.0/plan

The Jakarta Activation 2.0 specification follows the release plan for Jakarta
EE 9.  In addition, it introduces a minor incompatible change. 
More detail can be found in the Release Plan record.

Thanks!

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


-- 
The Eclipse Management Organization
Eclipse Foundation

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.