[
https://issues.apache.org/jira/browse/QPID-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159176#comment-17159176
]
Robert Godfrey commented on QPID-8455:
--------------------------------------
[~orudyy] Personally I think it's acceptable to simply do the renames on the
master branch for the next release that comes off that, and leave the existing
names on the older, maintenance, release streams. We should signal that
allow/deny list are the correct terms going forward - but for historic releases
we won't break compatibility. This is inline with the approach I seeing
followed in other projects.
> [Broker-J]Use allow/deny list terminology for existing attributes and context
> variables
> ---------------------------------------------------------------------------------------
>
> Key: QPID-8455
> URL: https://issues.apache.org/jira/browse/QPID-8455
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Dedeepya
> Priority: Major
> Fix For: qpid-java-broker-8.0.1, qpid-java-broker-7.1.9
>
>
> Rename attributes and context variables containing the term white/black list
> to allow/deny list.
> The names allow/deny list are more inlined with current industry naming
> standards.
> Example:
> The port derived attributes tlsCipherSuiteWhiteList and
> tlsCipherSuiteBlackList will have to be renamed to tlsCipherSuiteAllowList
> and tlsCipherSuiteDenyList respectively.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
