| Re: [jakartabatch-dev] Project Directions |
_______________________________________________Hi Scott,I am new to this project can you give me small issues to begin with?Thanks and Regards,NishantOn Sun, Mar 8, 2020, 4:47 AM Scott Kurz <skurz@xxxxxxxxxx> wrote:_______________________________________________Hi all,
As we've gotten some offers to help with the project, let me write this kickoff email saying where I see us starting from. At the moment, of course, nothing much is happening so this is just my opinion, and by no means the final word.
What is the short term goal?
To release Batch 2.0 as part of Jakarta EE 9. As the package rename ("big bang") from javax.* => jakarta.* will be the only (or almost the only?) change, this is not the most exciting work.
https://github.com/eclipse-ee4j/batch-api/issues/7
What next after that?
So let me give my take on the project, which I captured in outline form here: https://github.com/eclipse-ee4j/batch-api/wiki/Project-Directions
I'd like to leverage the work we're going to do to release Jakarta EE 9 and the buzz to build enough momentum to carry us to releasing some new enhancements, maybe later in the year, maybe as part of a new EE platform release (or maybe on its own even).
The exact directions and priorities are up to whatever community we generate here. But I can start by tackling some obstacles I know lie ahead, and also help keep alive some of the collective knowledge we've built in the earlier project.
What about the old issues from the former project?
My take, (and I'm just throwing this out there, you can disagree and propose a different approach), is that we start with a clean slate and do NOT just automatically move over the old issues.
So the ONLY official issues would now be here:
SPEC/API - https://github.com/eclipse-ee4j/batch-api
TCK - https://github.com/eclipse-ee4j/batch-tck/
Now, I recognize we've had some discussions worth coming back to, but from a variety of sources. I did make an attempt at collecting one set of issues, including the old JSR 352 issues here: https://github.com/eclipse-ee4j/batch-api/wiki/Legacy-Issues
If someone cares enough to go and open new issues for each of these, I'm not going to stop them. I plan to review to some degree and (re)open issues myself.
But I don't want to take the stance that, until we've gone through and filtered and prioritized this large issue set, we cannot do anything new. Maybe before we put in a release plan we well, maybe we won't, I don't think we have to decide just yet. Let's wait until we are making some progress first.
What do we need to clarify before working on new function?
I'm going to elaborate in separate emails, but I at least captured the two big issues I see us needing to clarify to really move forward:
1) The future of Batch in the Glassfish runtime
2) How to add TCK tests that potentially break existing impls passing the 1.0.x TCK:
What can I do to contribute in the meantime?
I put up some ideas such as doc, website, TCK automation (convert to Arquillian), etc.
https://github.com/eclipse-ee4j/batch-api/wiki/Ways-To-Contribute
Finally, I know this email has gotten a bit long.. feel free to break down any replies / follow-ups in separate threads.
Thanks for your interest,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev