Re: [DISCUSS] Draft proposal for terminology change

[Bruce Snyder]

FWIW, there is already a ticket for the work:

https://issues.apache.org/jira/browse/AMQ-7514

Bruce

On Sat, Jul 25, 2020 at 12:25 PM Matt Pavlovich  wrote:

> Kicking off draft proposal conversation, we can then convert this to a
> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> sure I’ve missed some key points and am not married to anything here.
> Please chime in!
>
> Description: Support migration of terms such as ‘master’ and ’slave’.
>
> Proposed steps:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> 6. Other?
>
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
>
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
>
> Thanks,
> Matt Pavlovich



-- 
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61Ehttp://bsnyder.org/ 

Re: [DISCUSS] Draft proposal for terminology change

[Timothy Bish]

On 7/25/20 2:24 PM, Matt Pavlovich wrote:

Kicking off draft proposal conversation, we can then convert this to a ticket. 
I’ve collected ideas from the recent dev mailing list convo. I’m sure I’ve 
missed some key points and am not married to anything here. Please chime in!

Description: Support migration of terms such as ‘master’ and ’slave’.

Proposed steps:
1. Deprecate terms such as ‘master’ and ’slave
2. log.warn any configuration change notifications
3. Provide compatibility under the covers for deprecated terms
4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
5. Notify users in an announcement and provide a conversion HOWTO
6. Other?

New terms:
a. For shared storage: ‘active’ and ’standby’
b. For replication: ‘primary’ and ‘replica'

For example:
‘master’ -> ‘active’
’slave’ -> ’standby'

Thanks,
Matt Pavlovich


+1


--
Tim Bish

Re: [DISCUSS] Draft proposal for terminology change

[Matt Pavlovich]

Hey Clebert-

Good point. Perhaps clarifying that the terms may remain in the code base 
during Phase 1 for backwards compatibility and migration assistance logging 
notification. Then in a Phase 2. the terms are fully removed from codebase.

[Draft rev 3]

Kicking off draft proposal conversation, we can then convert this to a
ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
sure I’ve missed some key points and am not married to anything here.
Please chime in!

Description: Support migration of terms such as ‘master’ and ’slave’.

Phases to be implemented as separate JIRA tickets.

Phase 1: 
1. Deprecate terms such as ‘master’ and ’slave
2. log.warn any configuration change notifications
3. Provide compatibility under the covers for deprecated terms
4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
5. Notify users in an announcement and provide a conversion HOWTO

Phase 2: 
1. Remove terminology as part of a major or minor release (SEMVER where ‘y’ in 
‘x.y.z’ is minor version number)

New terms:
a. For shared storage: ‘active’ and ’standby’
b. For replication: ‘primary’ and ‘replica'
c. For 'white list' and 'blacklist': 'allow list' and 'deny list'

For example:
‘master’ -> ‘active’
’slave’ -> ’standby'

Thanks,
Matt Pavlovich

> On Jul 26, 2020, at 11:13 AM, Clebert Suconic  
> wrote:
> 
>> [Draft rev 2]
>> 
>> Kicking off draft proposal conversation, we can then convert this to a
>> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
>> sure I’ve missed some key points and am not married to anything here.
>> Please chime in!
>> 
>> Description: Support migration of terms such as ‘master’ and ’slave’.
>> 
>> Proposed steps:
>> 1. Deprecate terms such as ‘master’ and ’slave
>> 2. log.warn any configuration change notifications
>> 3. Provide compatibility under the covers for deprecated terms
>> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
>> 5. Notify users in an announcement and provide a conversion HOWTO
>> 6. Other?
>> 
>> New terms:
>> a. For shared storage: ‘active’ and ’standby’
>> b. For replication: ‘primary’ and ‘replica'
>> c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
>> 
>> For example:
>> ‘master’ -> ‘active’
>> ’slave’ -> ’standby'
>> 
>> Thanks,
>> Matt Pavlovich

Re: [DISCUSS] Draft proposal for terminology change

[Daniel Kulp]

Huge +1 from me.   Major thanks for putting a concrete proposal together.

-- 
Daniel Kulp
dk...@apache.org  - http://dankulp.com/blog 

Talend - http://talend.com 



> On Jul 25, 2020, at 11:39 PM, Matt Pavlovich  wrote:
> 
> Clebert— Good catch, updated below 
> 
> [Draft rev 2]
> 
> Kicking off draft proposal conversation, we can then convert this to a
> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> sure I’ve missed some key points and am not married to anything here.
> Please chime in!
> 
> Description: Support migration of terms such as ‘master’ and ’slave’.
> 
> Proposed steps:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> 6. Other?
> 
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
> c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
> 
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
> 
> Thanks,
> Matt Pavlovich
> 
> 
> 
> 
>> On Jul 25, 2020, at 6:58 PM, Clebert Suconic  
>> wrote:
>> 
>> You’re missing blacklist and white list.
>> 
>> 
>> Should be allow list.  And deny list.
>> 
>> On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich  wrote:
>> 
>>> Kicking off draft proposal conversation, we can then convert this to a
>>> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
>>> sure I’ve missed some key points and am not married to anything here.
>>> Please chime in!
>>> 
>>> Description: Support migration of terms such as ‘master’ and ’slave’.
>>> 
>>> Proposed steps:
>>> 1. Deprecate terms such as ‘master’ and ’slave
>>> 2. log.warn any configuration change notifications
>>> 3. Provide compatibility under the covers for deprecated terms
>>> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
>>> 5. Notify users in an announcement and provide a conversion HOWTO
>>> 6. Other?
>>> 
>>> New terms:
>>> a. For shared storage: ‘active’ and ’standby’
>>> b. For replication: ‘primary’ and ‘replica'
>>> 
>>> For example:
>>> ‘master’ -> ‘active’
>>> ’slave’ -> ’standby'
>>> 
>>> Thanks,
>>> Matt Pavlovich
>> 
>> -- 
>> Clebert Suconic
> 

Re: [DISCUSS] Draft proposal for terminology change

[Christopher Shannon]

+1, looks good to me so far.  I like those terms and think they make more
sense and are more descriptive than the old terms.

I can help work on the OpenWire changes in 5.x and Artemis to make sure
everything is backwards compatible once everyone agrees.

For logging, the warn level is probably ok. Ideally you'd want someone to
be notified they are using old and deprecated terms and should update when
they can.

On Mon, Jul 27, 2020 at 12:36 AM Jean-Baptiste Onofre 
wrote:

> +1 with the new terms.
>
> I think we can plan this step by step for new releases and
> website/documentation update (with the corresponding Jira for tracking).
>
> Regards
> JB
>
> > Le 26 juil. 2020 à 05:39, Matt Pavlovich  a écrit :
> >
> > Clebert— Good catch, updated below
> >
> > [Draft rev 2]
> >
> > Kicking off draft proposal conversation, we can then convert this to a
> > ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> > sure I’ve missed some key points and am not married to anything here.
> > Please chime in!
> >
> > Description: Support migration of terms such as ‘master’ and ’slave’.
> >
> > Proposed steps:
> > 1. Deprecate terms such as ‘master’ and ’slave
> > 2. log.warn any configuration change notifications
> > 3. Provide compatibility under the covers for deprecated terms
> > 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> > 5. Notify users in an announcement and provide a conversion HOWTO
> > 6. Other?
> >
> > New terms:
> > a. For shared storage: ‘active’ and ’standby’
> > b. For replication: ‘primary’ and ‘replica'
> > c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
> >
> > For example:
> > ‘master’ -> ‘active’
> > ’slave’ -> ’standby'
> >
> > Thanks,
> > Matt Pavlovich
> >
> >
> >
> >
> >> On Jul 25, 2020, at 6:58 PM, Clebert Suconic 
> wrote:
> >>
> >> You’re missing blacklist and white list.
> >>
> >>
> >> Should be allow list.  And deny list.
> >>
> >> On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich 
> wrote:
> >>
> >>> Kicking off draft proposal conversation, we can then convert this to a
> >>> ticket. I’ve collected ideas from the recent dev mailing list convo.
> I’m
> >>> sure I’ve missed some key points and am not married to anything here.
> >>> Please chime in!
> >>>
> >>> Description: Support migration of terms such as ‘master’ and ’slave’.
> >>>
> >>> Proposed steps:
> >>> 1. Deprecate terms such as ‘master’ and ’slave
> >>> 2. log.warn any configuration change notifications
> >>> 3. Provide compatibility under the covers for deprecated terms
> >>> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and
> Artemis
> >>> 5. Notify users in an announcement and provide a conversion HOWTO
> >>> 6. Other?
> >>>
> >>> New terms:
> >>> a. For shared storage: ‘active’ and ’standby’
> >>> b. For replication: ‘primary’ and ‘replica'
> >>>
> >>> For example:
> >>> ‘master’ -> ‘active’
> >>> ’slave’ -> ’standby'
> >>>
> >>> Thanks,
> >>> Matt Pavlovich
> >>
> >> --
> >> Clebert Suconic
> >
>
>

Re: [DISCUSS] Draft proposal for terminology change

[Jean-Baptiste Onofre]

+1 with the new terms.

I think we can plan this step by step for new releases and 
website/documentation update (with the corresponding Jira for tracking).

Regards
JB

> Le 26 juil. 2020 à 05:39, Matt Pavlovich  a écrit :
> 
> Clebert— Good catch, updated below 
> 
> [Draft rev 2]
> 
> Kicking off draft proposal conversation, we can then convert this to a
> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> sure I’ve missed some key points and am not married to anything here.
> Please chime in!
> 
> Description: Support migration of terms such as ‘master’ and ’slave’.
> 
> Proposed steps:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> 6. Other?
> 
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
> c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
> 
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
> 
> Thanks,
> Matt Pavlovich
> 
> 
> 
> 
>> On Jul 25, 2020, at 6:58 PM, Clebert Suconic  
>> wrote:
>> 
>> You’re missing blacklist and white list.
>> 
>> 
>> Should be allow list.  And deny list.
>> 
>> On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich  wrote:
>> 
>>> Kicking off draft proposal conversation, we can then convert this to a
>>> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
>>> sure I’ve missed some key points and am not married to anything here.
>>> Please chime in!
>>> 
>>> Description: Support migration of terms such as ‘master’ and ’slave’.
>>> 
>>> Proposed steps:
>>> 1. Deprecate terms such as ‘master’ and ’slave
>>> 2. log.warn any configuration change notifications
>>> 3. Provide compatibility under the covers for deprecated terms
>>> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
>>> 5. Notify users in an announcement and provide a conversion HOWTO
>>> 6. Other?
>>> 
>>> New terms:
>>> a. For shared storage: ‘active’ and ’standby’
>>> b. For replication: ‘primary’ and ‘replica'
>>> 
>>> For example:
>>> ‘master’ -> ‘active’
>>> ’slave’ -> ’standby'
>>> 
>>> Thanks,
>>> Matt Pavlovich
>> 
>> -- 
>> Clebert Suconic
> 

Re: [DISCUSS] Draft proposal for terminology change

[Clebert Suconic]

+1000 on everything


Not -1.. just asking a question on what to do in case old configs are
in place. We mentioned log.warn something like (Hey. .change to the
new term);

Do we really want to do the log.warn, or should we just silently load
it as we do for other deprecated terms?

On Sat, Jul 25, 2020 at 11:39 PM Matt Pavlovich  wrote:
>
> Clebert— Good catch, updated below
>
> [Draft rev 2]
>
> Kicking off draft proposal conversation, we can then convert this to a
> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> sure I’ve missed some key points and am not married to anything here.
> Please chime in!
>
> Description: Support migration of terms such as ‘master’ and ’slave’.
>
> Proposed steps:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> 6. Other?
>
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
> c. For 'white list' and 'blacklist': 'allow list' and 'deny list'
>
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
>
> Thanks,
> Matt Pavlovich
>
>
>
>
> > On Jul 25, 2020, at 6:58 PM, Clebert Suconic  
> > wrote:
> >
> > You’re missing blacklist and white list.
> >
> >
> > Should be allow list.  And deny list.
> >
> > On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich  wrote:
> >
> >> Kicking off draft proposal conversation, we can then convert this to a
> >> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> >> sure I’ve missed some key points and am not married to anything here.
> >> Please chime in!
> >>
> >> Description: Support migration of terms such as ‘master’ and ’slave’.
> >>
> >> Proposed steps:
> >> 1. Deprecate terms such as ‘master’ and ’slave
> >> 2. log.warn any configuration change notifications
> >> 3. Provide compatibility under the covers for deprecated terms
> >> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> >> 5. Notify users in an announcement and provide a conversion HOWTO
> >> 6. Other?
> >>
> >> New terms:
> >> a. For shared storage: ‘active’ and ’standby’
> >> b. For replication: ‘primary’ and ‘replica'
> >>
> >> For example:
> >> ‘master’ -> ‘active’
> >> ’slave’ -> ’standby'
> >>
> >> Thanks,
> >> Matt Pavlovich
> >
> > --
> > Clebert Suconic
>


-- 
Clebert Suconic

Re: [DISCUSS] Draft proposal for terminology change

[Matt Pavlovich]

Clebert— Good catch, updated below 

[Draft rev 2]

Kicking off draft proposal conversation, we can then convert this to a
ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
sure I’ve missed some key points and am not married to anything here.
Please chime in!

Description: Support migration of terms such as ‘master’ and ’slave’.

Proposed steps:
1. Deprecate terms such as ‘master’ and ’slave
2. log.warn any configuration change notifications
3. Provide compatibility under the covers for deprecated terms
4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
5. Notify users in an announcement and provide a conversion HOWTO
6. Other?

New terms:
a. For shared storage: ‘active’ and ’standby’
b. For replication: ‘primary’ and ‘replica'
c. For 'white list' and 'blacklist': 'allow list' and 'deny list'

For example:
‘master’ -> ‘active’
’slave’ -> ’standby'

Thanks,
Matt Pavlovich




> On Jul 25, 2020, at 6:58 PM, Clebert Suconic  
> wrote:
> 
> You’re missing blacklist and white list.
> 
> 
> Should be allow list.  And deny list.
> 
> On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich  wrote:
> 
>> Kicking off draft proposal conversation, we can then convert this to a
>> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
>> sure I’ve missed some key points and am not married to anything here.
>> Please chime in!
>> 
>> Description: Support migration of terms such as ‘master’ and ’slave’.
>> 
>> Proposed steps:
>> 1. Deprecate terms such as ‘master’ and ’slave
>> 2. log.warn any configuration change notifications
>> 3. Provide compatibility under the covers for deprecated terms
>> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
>> 5. Notify users in an announcement and provide a conversion HOWTO
>> 6. Other?
>> 
>> New terms:
>> a. For shared storage: ‘active’ and ’standby’
>> b. For replication: ‘primary’ and ‘replica'
>> 
>> For example:
>> ‘master’ -> ‘active’
>> ’slave’ -> ’standby'
>> 
>> Thanks,
>> Matt Pavlovich
> 
> -- 
> Clebert Suconic

Re: [DISCUSS] Draft proposal for terminology change

[Clebert Suconic]

You’re missing blacklist and white list.


Should be allow list.  And deny list.

On Sat, Jul 25, 2020 at 2:25 PM Matt Pavlovich  wrote:

> Kicking off draft proposal conversation, we can then convert this to a
> ticket. I’ve collected ideas from the recent dev mailing list convo. I’m
> sure I’ve missed some key points and am not married to anything here.
> Please chime in!
>
> Description: Support migration of terms such as ‘master’ and ’slave’.
>
> Proposed steps:
> 1. Deprecate terms such as ‘master’ and ’slave
> 2. log.warn any configuration change notifications
> 3. Provide compatibility under the covers for deprecated terms
> 4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
> 5. Notify users in an announcement and provide a conversion HOWTO
> 6. Other?
>
> New terms:
> a. For shared storage: ‘active’ and ’standby’
> b. For replication: ‘primary’ and ‘replica'
>
> For example:
> ‘master’ -> ‘active’
> ’slave’ -> ’standby'
>
> Thanks,
> Matt Pavlovich

-- 
Clebert Suconic

[DISCUSS] Draft proposal for terminology change

[Matt Pavlovich]

Kicking off draft proposal conversation, we can then convert this to a ticket. 
I’ve collected ideas from the recent dev mailing list convo. I’m sure I’ve 
missed some key points and am not married to anything here. Please chime in!

Description: Support migration of terms such as ‘master’ and ’slave’.

Proposed steps:
1. Deprecate terms such as ‘master’ and ’slave
2. log.warn any configuration change notifications
3. Provide compatibility under the covers for deprecated terms
4. Provide any openwire compatibility changes b/w ActiveMQ 5 and Artemis
5. Notify users in an announcement and provide a conversion HOWTO
6. Other?

New terms:
a. For shared storage: ‘active’ and ’standby’
b. For replication: ‘primary’ and ‘replica'

For example:
‘master’ -> ‘active’
’slave’ -> ’standby'

Thanks,
Matt Pavlovich