Santiago, thank you for setting up this epic. Two questions: (a) Why using new branch instead of using master? (b) Can you please set the checkboxes on those tasks that are already finished? It is confusing that some tasks in the epic are unchecked but contain the word "DONE". So what is the state of these? Thanks -Markus Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Santiago Pericasgeertsen
Gesendet: Montag, 26. Juni 2023 17:40
An: Jakarta Rest project developer discussions
Betreff: Re: [rest-dev] Jakarta REST work for EE 11 On May 22, 2023, at 9:30 AM, Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx> wrote: Dear Jakarta REST experts,
As all of you know, Jakarta EE 11 planning is now underway. We are being asked to create a PR on the specifications repo and get the work started on the new API. Our current plan, which seems to align very nicely with the EE platform goals, is to make changes to the REST API and specification to better integrate with CDI, as a way to simplify our "injection strategy" and also to better integrate with other specifications.
Unfortunately, it is unlikely I will be able to commit substantially to this effort before the last couple of months of the year. The purpose of this communication is to __ask for help__ during this period in order to start the work ASAP. I should be able to review parts of the work submitted in the next few months, but will not have the time to create it myself.
The initial step should be to create at least one GitHub epic from which we can create individual issues for people to investigate. I volunteer to create such an epic and thus help kickstart the new API and spec work.
Feel free to extend, link issues, creates issues from Epic, etc. See also branch 'release-4.0'. Hopefully this epic can get us going with the 4.0 work. Thanks for those that already volunteered. |
