Re: [jakarta.ee-spec] Updating spec pages (was: Fwd: [jakartaee/specific

["Kevin Sutter" <sutter@xxxxxxxxxx>]

I will second Ivar's
description of the meeting yesterday.  Since NoSQL is "(under
development)", then updating preliminary versions of their specs,
apis, tcks, etc should be a normal development practice.  We shouldn't
require additional process to keep this development page up-to-date (other
than a Spec Committee member review, approval, and merge).

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

Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)



From:
       Ivar
Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
To:
       Jakarta
specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Date:
       04/08/2021
01:15
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec] Updating spec pages (was: Fwd: [jakartaee/specifications]
Nosql Status update (#333))
Sent
by:        "jakarta.ee-spec"
<jakarta.ee-spec-bounces@xxxxxxxxxxx>

---

Hi David,

It was decided on the Spec Committee
call yesterday that small updates (such as updating to a new Milestone
of the artifacts) are OK as long as the update is for a Non-Final version
of the spec that is under development. 
The key here is Under Development.
Everyone present agreed. Ed was there as well. 

For this special case, NoSQL is not due
for a progress review within the next 6 months. According to the JESP,
they can produce milestones as they wish without any review from the specification
committee. 
Keeping this page up-to-date seems like
the right thing to do.

Ivar

On Wed, Apr 7, 2021 at 11:44 PM David
Blevins <dblevins@xxxxxxxxxxxxx>
wrote:
I know Ed and myself have both raised
the point we think what appears on the spec pages should represent what
has actually been approved by the spec committee via the JESP.  Ed,
feel free to clarify as needed.

Raising this up so we do not consider
this action to be setting precedent and there is still room to discuss
for future PRs.


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

Begin forwarded message:

From: Ivar
Grimstad <notifications@xxxxxxxxxx>
Subject:
Re: [jakartaee/specifications] Nosql Status update (#333)
Date: April
7, 2021 at 6:56:37 AM PDT
To: jakartaee/specifications
<specifications@xxxxxxxxxxxxxxxxxx>
Cc: Subscribed
<subscribed@xxxxxxxxxxxxxxxxxx>
Reply-To:
jakartaee/specifications <reply+AAAXFTS37LOUCG4PUUELNQ56PGNRLEVBNHHDBTVDAM@xxxxxxxxxxxxxxxx>


As discussed on the spec committee call
today, this is good to go.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view
it on GitHub,
or unsubscribe.

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation- Community. Code. Collaboration. _______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec