Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Your feedback please: Pulling together TCK Release Plan for Jakarta EE 9.1 


On 11/17/20 2:06 PM, Ed Bratt wrote:
In the Platform committee meeting this morning, we discussed several topics, one of which was the goal of supporting JDK 11. I understand that the Platform TCK and the component TCKs that come from this project have been doing some preliminary work that will lead to JDK 11 support. I'd like to use this as a way to consolidate some of the answers and questions that that preliminary work has shown.
I'd like us to start to write down the the goals and questions that remain for this effort. As I understand it, this project doesn't have a specific Eclipse release review requirement or Specification ballot requirement -- instead, we are responsible for supplying TCKs to several other component projects. So, some of this work will be to solicit the goals from other component APIs so that we can better plan work in this project. 

+1
I would hope that this plan describes the basic plans around JDK 11 support -- one TCK or two (I think the former) -- if there is any effort that will be applied to TCK refactoring (i.e. moving any TCKs to external projects) -- if we plan to invest in any modifications to the TCK tooling -- anything else that we might intend to accomplish for this next release.
Does anyone know when do we have to update to a newer version of the TCK signature test tooling? Are we covered up to a certain JDK version currently?
If we ever create our own signature test tooling or fork, we should look at removing the JDK signatures from what we test against (https://github.com/eclipse-ee4j/jakartaee-tck/issues/156).
For timing -- I think the ideal would be that this release be planned for mid 2021 -- but that isn't formalized anywhere -- just something to shoot for.
I plan to start capturing this in a document -- probably a .md that I'll check into the repository (and we'll update to the GH Pages web-site).
+1 for using TCK GH Pages web-site. Time permitting, I would like to move most of our Platform TCK wiki content over there using a folder structure based on different EE versions. (e.g. 9.1.x).
Our goal should be to support a Plan review for each specification component -- primarily the Jakarta EE 9.1 platform -- but if other work is considered and would be needed, we ought to note it. 

IMO, we should note all of the various TCKs including the non-Platform-TCKs.
I want to kick this off with this e-mail -- please reply if you think you have "big" goals that you think need to be achieved. 

We'll follow that with discussion about how we'll make these changes


+1
And then, whatever external goals we think we'll be asked to deliver for component projects (for example, there is some work going on with Faces that will likely involve work from us here in the TCK team.) 

In summary:

    Defining Goals: Add support for JDK 11

    Core work: Generate Jenkins jobs to verify compatible
    implementations; Enhance TCK to support JDK 11 as well as JDK 8.
    (Decide about build requirements)

    Required Deliverables: Deliver suitable TCK updates for all included
    component API projects (personally, I would like to see that we
    provide JDK 8 and 11 support for compatible implementation
    verification -- but that's certainly just an ideal right now.)

    Target time-frame: mid-year 2021 (for planning purposes, we will
    adjust if the overall program changes)
IMO, it would be good to have initial time estimates for all parts non-platform-tck + other TCKs, GlassFish JDK11 support 



    Additional goals: Support Faces project in efforts to simplify and
    refactor Faces TCK; Support feature changes for Restful Web
    Services; Clean-up/reorganize CI jobs for clarity; Improve community
    awareness/adoption/contributions to TCK project operations
On additional goals, is there a central place that we should discuss the efforts to simply and refactor various SPEC API TCKs that currently are in the Platform TCK? IMO, at a minimum we should discuss what will likely remain in the Platform TCK. 

So far, we have the following various discussions:
- "Turning TCK into a multi-dependency maven project" https://github.com/eclipse-ee4j/jakartaee-tck/issues/51 + https://www.eclipse.org/lists/jakartaee-tck-dev/msg00111.html - "Consume Jakarta Batch tests from batch-tck rather than duplicating within this project" https://github.com/eclipse-ee4j/jakartaee-tck/issues/574 - "Possible ways to use Arquillian in Jakarta EE TCKs" https://ondro.inginea.eu/index.php/possible-ways-to-use-arquillian-in-jakarta-ee-tcks/ - "Guide to contributing to Jakarta EE 10" https://docs.google.com/document/d/1uZFBoIujXCc-gQhCzh_ZdlKEsrsV0yVVIHzBTI3usF8/edit - "Modernising the Servlet TCK" https://www.eclipse.org/lists/servlet-dev/msg00287.html + https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00671.html - The above mentioned "Updating TCK removal of JSP" https://www.eclipse.org/lists/faces-dev/msg00054.html 



Please add your initial thoughts by replying to this thread.
Once that settles a bit, we can move it to a real document -- which will become our plan proposal. 

Thanks Ed for pulling this together!

Scott



Thanks,

-- Ed


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

Back to the top