| [jakarta.ee-spec.committee] Leftover JSRs? |
Hi, I was almost about to ask this in a previous call, but the time is Always a bit short. Beside JNoSQL which luckily did not even bother proposing a new JSR at JCP any more, two other JSRs that are non-final were mentioned as possible candidates for new Jakarta EE Specs. Config (which I also mentioned) and MVC, which Ivar suggested in a Prior call. When I saw he and Christian got the latest Star Spec Lead I thought „well-deserved, they got their MVC JSR final“ but it turns out, it is also not final yet, but still in Proposed Final Draft since around Code One 2018. What shall happen to those two „Zombie JSRs“ that are in a „Twilight Zone“ between not even filed an EDR yet (Config) and Proposed Final Draft for 6 months now (MVC) ? Will either of them ever undergo a Final Approval Ballot in the JCP EC and go Final or shall both of them continue under Jakarta EE, but then why have the Spec Leads not withdrawn them in favor of Jakarta EE? (or in case of Config there’s an extra complication because most work is done in the NON-STANDARD MicroProfile right now) The JCP has often been perceived as „slow“ but it isn’t only Oracle’s fault, neither of these JSRs are led by Oracle now. And those they still have at JCP work at a really fast pace, whether 2 full Major version JDKs each are good and useful, that’s another question, but they are delivered on time. Regards, Werner |