Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jta-dev] Jakarta Transactions 2.0 for Jakarta EE 9 remaining items
I think I have updated the release record, scheduled IP log, emaile PMC, started a release review by emailing EMO. So of those four I think I am not going to check "Generated IP Log" but will check the others.

On Thu, 8 Oct 2020 at 12:07, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
This is the spec "staging" tag: https://github.com/eclipse-ee4j/jta-api/tree/specification-2.0-staging (I called it staging in case we need to reissue another "Final Release" into https://github.com/jakartaee/specifications/pull/265 before it is merged)

On Thu, 8 Oct 2020 at 12:05, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
https://github.com/jakartaee/specifications/pull/265 is updated with the details of the Final Release of the spec and so on.

Need to look into:
Updated release record
Generated IP Log
Email to PMC
Start release review by emailing EMO

On Wed, 7 Oct 2020 at 15:24, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
I expect to proceed Thursday morning (UTC+1) sometime with producing a Final Release of the specification and updating https://github.com/jakartaee/specifications/pull/265

Updated release record
Generated IP Log
Email to PMC
Start release review by emailing EMO

But I will try to work out what to do.


On Tue, 6 Oct 2020 at 17:10, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
That is merged, so I think we have everything we will need merged now and we can move forward with producing final versions of the docs and finalising https://github.com/jakartaee/specifications/pull/265

On Tue, 6 Oct 2020 at 16:06, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
To update this thread, I think we are waiting on https://github.com/eclipse-ee4j/glassfish/pull/23222 being merged and then the relevant page being available at https://eclipse-ee4j.github.io/glassfish/certifications/jakarta-transactions/2.0/TCK-Results

On Fri, 2 Oct 2020 at 12:22, Lance Andersen <LANCE.ANDERSEN@xxxxxxxxxx> wrote:


On Oct 2, 2020, at 6:38 AM, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:



On Thu, 1 Oct 2020 at 23:47, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
On Oct 1, 2020, at 5:34 AM, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:

On Thu, 1 Oct 2020 at 09:56, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:


On Wed, 30 Sep 2020 at 11:42, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:


On Wed, 30 Sep 2020 at 01:50, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
Great progress.  Do you think we could be complete end of day Thursday so that the spec committee could start the final ballot Friday morning?


It depends a bit on whether we need the TCK promoted (please see below) and how easy it is to do the certification request correctly (I assume we need to use a build provided by Glassfish and so we probably need to synchronize with them - please see below).

Perhaps we could use a weekly build of Glassfish but given when I released the recent updated Jakarta Transactions that weekly build of Glassfish I guess will be on the 4th October:

I don't have an ETA for the TCK to be promoted yet so that is an unknown right now:

Once we have those we can prepare the certification request - can we raise that when we just have a PR on glassfish for them to update their website or does the page need to be live?

I have provided an update in https://github.com/eclipse-ee4j/jta-api/issues/156 for the next steps 

Sounds great.  Looks like Scott is awaiting your go-head to promote the TCK and when that is done those steps in #156 look very accurate.

While that's in progress, could you check off some of the items on this checklist?


These items can all be done now:

 - Specification PDF in the form of jakarta-wombat-spec-x.y.pdf
 - Specification HTML in the form of jakarta-wombat-spec-x.y.html
 - A specification page named _index.md without final branding and versions
 - Specification JavaDoc in the wombat/x.y/apidocs directory

I haven't generated a Final version of the specification yet - I could do it now but if we regenerate it then I am wondering if it might be a bit strange to have multiple versions that have the word final in?

I would suggest not marking anything final until you are actually final with all of the bits as the spec and the javadoc make up the full spec.  So one should not be final without the other in a publicly available forum.  

It would lead to a bit of confusion….

I can certainly update the PR with the last draft though. That said, I may have generated a final version of the Javadocs (and unless we restage the API these shouldn't change) so I can update the PR with those and I can take a look at the _index.md. 


-David

_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
_______________________________________________
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jta-dev__;!!GqivPVa7Brio!J4l8iq4S61zmDyI99Cpo2QwNIkETiRqU2WRW_beIt2UWgE7oJRLb6qYQ3PBDiGRF1w$


Best
Lance
------------------



Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering 
1 Network Drive 
Burlington, MA 01803
Lance.Andersen@xxxxxxxxxx




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

Back to the top