[
https://issues.apache.org/jira/browse/AMQ-7309?focusedWorklogId=628944&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-628944
]
ASF GitHub Bot logged work on AMQ-7309:
---------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jul/21 09:21
Start Date: 28/Jul/21 09:21
Worklog Time Spent: 10m
Work Description: gemmellr commented on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-888154727
> That is an extreme edge use case-- one that is acceptable for a RC release.
I'm not sure I'd agree that bridging between different systems was
'extreme-edge'. Not the primary use, sure, but hardly strange and unusual
either.
Not sure I have seen mention of doing 'RC releases' before. Are these to be
named 5.17.0-rc1, rc2 etc given it is targeting main, or is it for after that
as a series of 5.18.0-rcX? Might seem odd to use 5.17.0 given that should
probably be out and done already (and would then be looking for 5.17.1 etc for
bug fixes), while this is unimplemented. Given that it even seems a stretch
calling it an -rc, to me that usually implies near-completion.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 628944)
Time Spent: 4h 10m (was: 4h)
> Add JMS 2.0 support
> -------------------
>
> Key: AMQ-7309
> URL: https://issues.apache.org/jira/browse/AMQ-7309
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, JMS client
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
