David, please review it, and submit for ballot. Although I
heard that plans that weren't submitted in time for April 15th
won't make it into Jakarta EE 10, I think we should try to
persuade the spec committee to accept it for EE 10 because JMS
is a very important spec that has a lot of potential to
modernize.
I agree with David that we most probably won't have
enough time to implement anything significant for Jakarta
EE 10 and that it's best to focus on the essential changes
first (fixes, repeatable annotations) and separating the
TCK to the JMS repository. We can work on features listed
in [1] too and
if they are ready, we can add them to plan via a Progress
Review later as David suggests.
I'd like to prepare a draft of the plan for JMS 3.1
soon, so that we have at least a chance to join the
Jakarta EE 10 release train.
We can discuss new features either in general on the
github issue [1] or start
a new thread on this mailing list for each specific
proposal.
So do we think we reached some kind of
consensus on which way to go? Do folks that have not
chimed in yet have an opinion?
Either way, I will go though the current issue
tracker and triage issues this week. I don’t think
that has been done in a while. If other folks can join
in, that would be awesome.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as
an individual community member and do not reflect
the views of my employer.
If we can't do that, we should go though the
issue tracker and gather some minor fix items. I
definitely think we should be able to able to
gather enough of those for a small maintenance
release.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as
an individual community member and do not
reflect the views of my employer.
On 5/4/2021 7:29 PM, Ondro Mihályi wrote:
Hi all,
I noticed that Messaging didn't submit a
plan for review for Jakarta EE 10. Do we
still want to submit a plan so that we can
deliver a new version of JMS in EE 10?
I think that plans should have been
submitted by April 15 but we may still try
to submit a plan because JMS is a very
important Jakarta EE specification. It
wouldn't be a good message if JMS didn't get
any update for EE 10, at least with very
minor updates.
Because we didn't have any discussion
about new features recently, we could
introduce something from the roadmap
outlined by David in 2019 in a github
issue. I would only go after things
that are rather straightforward, long
overdue, and already well documented. So
from the items in that issue, I suggest to
consider only:
Should we plan to add the new features as
I suggested above? Or it's much more that we
can handle and it's better to submit a plan
just to add fixes and possibly support
repeatable annotations?