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?
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….
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
|
