[
https://issues.apache.org/jira/browse/AMQ-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348658#comment-17348658
]
Timothy A. Bish commented on AMQ-7309:
--------------------------------------
>From what I can see the normal process applies here and a -1 on a code
>modification would still hold to the normal process. Since there's not been a
>PR there isn't any code to vote upon yet so please proceed as normal and raise
>a PR at which point it can be reviewed and remain subject to the standard
>rules of the foundation.
"Votes on *code modifications* follow a different model. In this scenario, a
negative vote constitutes a
[veto|https://www.apache.org/foundation/voting.html#Veto] , which the voting
group (generally the PMC of a project) cannot override. Again, this model may
be modified by a [lazy
consensus|https://www.apache.org/foundation/voting.html#LazyConsensus]
declaration when the request for a vote is raised, but the full-stop nature of
a negative vote does not change. Under normal (non-lazy consensus) conditions,
the proposal requires three positive votes and no negative votes in order to
pass; if it fails to garner the requisite amount of support, it doesn't. Then
the proposer either withdraws the proposal or modifies the code and resubmits
it, or the proposal simply languishes as an open issue until someone gets
around to removing it."
[https://www.apache.org/foundation/voting.html]
> 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
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
