Re: [PROPOSAL] Renaming terms

[Matt Pavlovich]

JB-

Are you referring to ‘Karaf Cave’ or ‘Karaf Runtime’?

I think with Karaf Runtime locking, the warm boot tends to be to not have all 
bundles active, for things that need to be singletons, such as scheduled jobs 
and pollers. The Karaf Runtime is running enough to be monitored, but generally 
not running any active workload. This is what I was referring to as ’standby’.

I think ‘primary’ and ‘replica’ work great for replication use cases.

-Matt

> On Jul 27, 2020, at 12:51 PM, Jean-Baptiste Onofre  wrote:
> 
> No, I don’t think it’s accurate to Karaf.
> 
> Standby means that the instance is not "active", but actually, in the case of 
> Karaf, it’s active and replicate the "master/active".
> 
> That’s why I proposed primary/secondary. We can also use active/replica if 
> you think it’s more accurate.
> 
> Regards
> JB
> 
>> Le 27 juil. 2020 à 18:26, Matt Pavlovich  a écrit :
>> 
>> My $0.02, the ‘primary’ ’secondary’ numeric-style terms can be misleading, 
>> since you can have multiple ’slave’ nodes and lock recovery is 
>> non-deterministic. So the ’secondary’ node doesn’t mean it is ’second’ in 
>> line to take over.
>> 
>> Thoughts on aligning with the proposed terms same as ActiveMQ?
>> 
>> master ->  ‘active’
>> slave -> ’standby'
>> 
>> -Matt Pavlovich
>> 
>>> On Jul 27, 2020, at 1:21 AM, Jean-Baptiste Onofre  wrote:
>>> 
>>> Hi guys,
>>> 
>>> I would like to propose new wording in some Karaf designs:
>>> 
>>> - In Karaf runtime, I would like to rename master/slave to primary/secondary
>>> - in Cellar, I would like to rename blacklist/whitelist to allowlist and 
>>> deny list
>>> 
>>> Thoughts ?
>>> 
>>> Regards
>>> JB
>> 
> 

Re: [PROPOSAL] Renaming terms

[Romain Manni-Bucau]

+0, it will make some people feel better (not sure but what i read) and
some other feel worse since it is 1-1 in terms of meaning and
positive/negative sense.
However it is a breaking change to be useful which hurts everyone so maybe
an user vote is better than a dev one?

Le lun. 27 juil. 2020 à 19:51, Jean-Baptiste Onofre  a
écrit :

> No, I don’t think it’s accurate to Karaf.
>
> Standby means that the instance is not "active", but actually, in the case
> of Karaf, it’s active and replicate the "master/active".
>
> That’s why I proposed primary/secondary. We can also use active/replica if
> you think it’s more accurate.
>
> Regards
> JB
>
> > Le 27 juil. 2020 à 18:26, Matt Pavlovich  a écrit :
> >
> > My $0.02, the ‘primary’ ’secondary’ numeric-style terms can be
> misleading, since you can have multiple ’slave’ nodes and lock recovery is
> non-deterministic. So the ’secondary’ node doesn’t mean it is ’second’ in
> line to take over.
> >
> > Thoughts on aligning with the proposed terms same as ActiveMQ?
> >
> > master ->  ‘active’
> > slave -> ’standby'
> >
> > -Matt Pavlovich
> >
> >> On Jul 27, 2020, at 1:21 AM, Jean-Baptiste Onofre 
> wrote:
> >>
> >> Hi guys,
> >>
> >> I would like to propose new wording in some Karaf designs:
> >>
> >> - In Karaf runtime, I would like to rename master/slave to
> primary/secondary
> >> - in Cellar, I would like to rename blacklist/whitelist to allowlist
> and deny list
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
> >
>
>

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

No, I don’t think it’s accurate to Karaf.

Standby means that the instance is not "active", but actually, in the case of 
Karaf, it’s active and replicate the "master/active".

That’s why I proposed primary/secondary. We can also use active/replica if you 
think it’s more accurate.

Regards
JB

> Le 27 juil. 2020 à 18:26, Matt Pavlovich  a écrit :
> 
> My $0.02, the ‘primary’ ’secondary’ numeric-style terms can be misleading, 
> since you can have multiple ’slave’ nodes and lock recovery is 
> non-deterministic. So the ’secondary’ node doesn’t mean it is ’second’ in 
> line to take over.
> 
> Thoughts on aligning with the proposed terms same as ActiveMQ?
> 
> master ->  ‘active’
> slave -> ’standby'
> 
> -Matt Pavlovich
> 
>> On Jul 27, 2020, at 1:21 AM, Jean-Baptiste Onofre  wrote:
>> 
>> Hi guys,
>> 
>> I would like to propose new wording in some Karaf designs:
>> 
>> - In Karaf runtime, I would like to rename master/slave to primary/secondary
>> - in Cellar, I would like to rename blacklist/whitelist to allowlist and 
>> deny list
>> 
>> Thoughts ?
>> 
>> Regards
>> JB
> 

Re: [PROPOSAL] Renaming terms

[Matt Pavlovich]

My $0.02, the ‘primary’ ’secondary’ numeric-style terms can be misleading, 
since you can have multiple ’slave’ nodes and lock recovery is 
non-deterministic. So the ’secondary’ node doesn’t mean it is ’second’ in line 
to take over.

Thoughts on aligning with the proposed terms same as ActiveMQ?

master ->  ‘active’
slave -> ’standby'

-Matt Pavlovich

> On Jul 27, 2020, at 1:21 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi guys,
> 
> I would like to propose new wording in some Karaf designs:
> 
> - In Karaf runtime, I would like to rename master/slave to primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and deny 
> list
> 
> Thoughts ?
> 
> Regards
> JB

Re: [PROPOSAL] Renaming terms

[Francois Papon]

LOL

François
fpa...@apache.org

Le 27/07/2020 à 16:37, Grzegorz Grzybek a écrit :
> But please don't use "trunk" - these days should be long gone ;)
>
> regards
> Grzegorz Grzybek
>
> pon., 27 lip 2020 o 16:19 Serge Huber  napisał(a):
>
>> wow I didn't think of the git branch name !
>>
>> But default seems to make more sense than main to me.
>>
>> Regards,
>>   Serge...
>>
>> On Mon, Jul 27, 2020 at 4:08 PM Jean-Baptiste Onofre 
>> wrote:
>>
>>> We can rename the branch anyway.
>>>
>>> I guess they gonna change the "default" soon.
>>>
>>> Regards
>>> JB
>>>
 Le 27 juil. 2020 à 16:06, Grzegorz Grzybek  a
>>> écrit :
 Isn't "master" hardcoded in `git` binary - when you create an empty git
 repo?

 $ cd /data/tmp/
 $ mkdir x
 $ cd x
 $ git init
 Initialized empty Git repository in /data/tmp/x/.git/
 $ git branch -vv
 $ git commit --allow-empty -m 'Initial commit'
 [master (root-commit) f402a8e] Initial commit
 $ git branch -vv
 * master f402a8e Initial commit

 regards
 Grzegorz Grzybek

 pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre 
>>> napisał(a):
> It sounds good, main is fine.
>
> I will do the rename and update documentation/website.
>
> Regards
> JB
>
>> Le 27 juil. 2020 à 14:55, Francois Papon <
>> francois.pa...@openobject.fr
> a écrit :
>> May be we could use the new github default branch name "main".
>>
>> regards,
>>
>> François
>> fpa...@apache.org
>>
>> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
>>> Yes, I forgot to mention this. I was about to propose develop branch
> instead of master branch.
>>> Regards
>>> JB
>>>
 Le 27 juil. 2020 à 14:37, Francois Papon <
>>> francois.pa...@openobject.fr>
> a écrit :
 Should we also rename "master" branch on git?

 regards,

 François
 fpa...@apache.org

 Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
> +1
>
> and wherever it fits best.
> Make sure the documentation is aligned, and maybe we could give
>>> hints
> in
> the current documentation already?
>
> regards, Achim
>
>
> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> lange.fab...@gmail.com>:
>
>> +1
>>
>> as a user of karaf 4.2 building our own distribution, we would be
> okay with
>> this being even in 4.2.x
>> Even when not backwards compatible
>>
>> Fabian
>>
>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
> j...@nanthrax.net>
>> wrote:
>>
>>> Hi guys,
>>>
>>> I would like to propose new wording in some Karaf designs:
>>>
>>> - In Karaf runtime, I would like to rename master/slave to
>>> primary/secondary
>>> - in Cellar, I would like to rename blacklist/whitelist to
> allowlist and
>>> deny list
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> JB
>
>>>

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

No way ;) trunk is for old guys ;)

Regards
JB

> Le 27 juil. 2020 à 16:37, Grzegorz Grzybek  a écrit :
> 
> But please don't use "trunk" - these days should be long gone ;)
> 
> regards
> Grzegorz Grzybek
> 
> pon., 27 lip 2020 o 16:19 Serge Huber  napisał(a):
> 
>> wow I didn't think of the git branch name !
>> 
>> But default seems to make more sense than main to me.
>> 
>> Regards,
>>  Serge...
>> 
>> On Mon, Jul 27, 2020 at 4:08 PM Jean-Baptiste Onofre 
>> wrote:
>> 
>>> We can rename the branch anyway.
>>> 
>>> I guess they gonna change the "default" soon.
>>> 
>>> Regards
>>> JB
>>> 
 Le 27 juil. 2020 à 16:06, Grzegorz Grzybek  a
>>> écrit :
 
 Isn't "master" hardcoded in `git` binary - when you create an empty git
 repo?
 
 $ cd /data/tmp/
 $ mkdir x
 $ cd x
 $ git init
 Initialized empty Git repository in /data/tmp/x/.git/
 $ git branch -vv
 $ git commit --allow-empty -m 'Initial commit'
 [master (root-commit) f402a8e] Initial commit
 $ git branch -vv
 * master f402a8e Initial commit
 
 regards
 Grzegorz Grzybek
 
 pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre 
>>> napisał(a):
 
> It sounds good, main is fine.
> 
> I will do the rename and update documentation/website.
> 
> Regards
> JB
> 
>> Le 27 juil. 2020 à 14:55, Francois Papon <
>> francois.pa...@openobject.fr
 
> a écrit :
>> 
>> May be we could use the new github default branch name "main".
>> 
>> regards,
>> 
>> François
>> fpa...@apache.org
>> 
>> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
>>> Yes, I forgot to mention this. I was about to propose develop branch
> instead of master branch.
>>> 
>>> Regards
>>> JB
>>> 
 Le 27 juil. 2020 à 14:37, Francois Papon <
>>> francois.pa...@openobject.fr>
> a écrit :
 
 Should we also rename "master" branch on git?
 
 regards,
 
 François
 fpa...@apache.org
 
 Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
> +1
> 
> and wherever it fits best.
> Make sure the documentation is aligned, and maybe we could give
>>> hints
> in
> the current documentation already?
> 
> regards, Achim
> 
> 
> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> lange.fab...@gmail.com>:
> 
>> +1
>> 
>> as a user of karaf 4.2 building our own distribution, we would be
> okay with
>> this being even in 4.2.x
>> Even when not backwards compatible
>> 
>> Fabian
>> 
>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
> j...@nanthrax.net>
>> wrote:
>> 
>>> Hi guys,
>>> 
>>> I would like to propose new wording in some Karaf designs:
>>> 
>>> - In Karaf runtime, I would like to rename master/slave to
>>> primary/secondary
>>> - in Cellar, I would like to rename blacklist/whitelist to
> allowlist and
>>> deny list
>>> 
>>> Thoughts ?
>>> 
>>> Regards
>>> JB
> 
> 
>>> 
>>> 
>> 

Re: [PROPOSAL] Renaming terms

[Grzegorz Grzybek]

But please don't use "trunk" - these days should be long gone ;)

regards
Grzegorz Grzybek

pon., 27 lip 2020 o 16:19 Serge Huber  napisał(a):

> wow I didn't think of the git branch name !
>
> But default seems to make more sense than main to me.
>
> Regards,
>   Serge...
>
> On Mon, Jul 27, 2020 at 4:08 PM Jean-Baptiste Onofre 
> wrote:
>
> > We can rename the branch anyway.
> >
> > I guess they gonna change the "default" soon.
> >
> > Regards
> > JB
> >
> > > Le 27 juil. 2020 à 16:06, Grzegorz Grzybek  a
> > écrit :
> > >
> > > Isn't "master" hardcoded in `git` binary - when you create an empty git
> > > repo?
> > >
> > > $ cd /data/tmp/
> > > $ mkdir x
> > > $ cd x
> > > $ git init
> > > Initialized empty Git repository in /data/tmp/x/.git/
> > > $ git branch -vv
> > > $ git commit --allow-empty -m 'Initial commit'
> > > [master (root-commit) f402a8e] Initial commit
> > > $ git branch -vv
> > > * master f402a8e Initial commit
> > >
> > > regards
> > > Grzegorz Grzybek
> > >
> > > pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre 
> > napisał(a):
> > >
> > >> It sounds good, main is fine.
> > >>
> > >> I will do the rename and update documentation/website.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >>> Le 27 juil. 2020 à 14:55, Francois Papon <
> francois.pa...@openobject.fr
> > >
> > >> a écrit :
> > >>>
> > >>> May be we could use the new github default branch name "main".
> > >>>
> > >>> regards,
> > >>>
> > >>> François
> > >>> fpa...@apache.org
> > >>>
> > >>> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
> >  Yes, I forgot to mention this. I was about to propose develop branch
> > >> instead of master branch.
> > 
> >  Regards
> >  JB
> > 
> > > Le 27 juil. 2020 à 14:37, Francois Papon <
> > francois.pa...@openobject.fr>
> > >> a écrit :
> > >
> > > Should we also rename "master" branch on git?
> > >
> > > regards,
> > >
> > > François
> > > fpa...@apache.org
> > >
> > > Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
> > >> +1
> > >>
> > >> and wherever it fits best.
> > >> Make sure the documentation is aligned, and maybe we could give
> > hints
> > >> in
> > >> the current documentation already?
> > >>
> > >> regards, Achim
> > >>
> > >>
> > >> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> > >> lange.fab...@gmail.com>:
> > >>
> > >>> +1
> > >>>
> > >>> as a user of karaf 4.2 building our own distribution, we would be
> > >> okay with
> > >>> this being even in 4.2.x
> > >>> Even when not backwards compatible
> > >>>
> > >>> Fabian
> > >>>
> > >>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
> > >> j...@nanthrax.net>
> > >>> wrote:
> > >>>
> >  Hi guys,
> > 
> >  I would like to propose new wording in some Karaf designs:
> > 
> >  - In Karaf runtime, I would like to rename master/slave to
> >  primary/secondary
> >  - in Cellar, I would like to rename blacklist/whitelist to
> > >> allowlist and
> >  deny list
> > 
> >  Thoughts ?
> > 
> >  Regards
> >  JB
> > >>
> > >>
> >
> >
>

Re: [PROPOSAL] Renaming terms

[Serge Huber]

wow I didn't think of the git branch name !

But default seems to make more sense than main to me.

Regards,
  Serge...

On Mon, Jul 27, 2020 at 4:08 PM Jean-Baptiste Onofre 
wrote:

> We can rename the branch anyway.
>
> I guess they gonna change the "default" soon.
>
> Regards
> JB
>
> > Le 27 juil. 2020 à 16:06, Grzegorz Grzybek  a
> écrit :
> >
> > Isn't "master" hardcoded in `git` binary - when you create an empty git
> > repo?
> >
> > $ cd /data/tmp/
> > $ mkdir x
> > $ cd x
> > $ git init
> > Initialized empty Git repository in /data/tmp/x/.git/
> > $ git branch -vv
> > $ git commit --allow-empty -m 'Initial commit'
> > [master (root-commit) f402a8e] Initial commit
> > $ git branch -vv
> > * master f402a8e Initial commit
> >
> > regards
> > Grzegorz Grzybek
> >
> > pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre 
> napisał(a):
> >
> >> It sounds good, main is fine.
> >>
> >> I will do the rename and update documentation/website.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 27 juil. 2020 à 14:55, Francois Papon  >
> >> a écrit :
> >>>
> >>> May be we could use the new github default branch name "main".
> >>>
> >>> regards,
> >>>
> >>> François
> >>> fpa...@apache.org
> >>>
> >>> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
>  Yes, I forgot to mention this. I was about to propose develop branch
> >> instead of master branch.
> 
>  Regards
>  JB
> 
> > Le 27 juil. 2020 à 14:37, Francois Papon <
> francois.pa...@openobject.fr>
> >> a écrit :
> >
> > Should we also rename "master" branch on git?
> >
> > regards,
> >
> > François
> > fpa...@apache.org
> >
> > Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
> >> +1
> >>
> >> and wherever it fits best.
> >> Make sure the documentation is aligned, and maybe we could give
> hints
> >> in
> >> the current documentation already?
> >>
> >> regards, Achim
> >>
> >>
> >> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> >> lange.fab...@gmail.com>:
> >>
> >>> +1
> >>>
> >>> as a user of karaf 4.2 building our own distribution, we would be
> >> okay with
> >>> this being even in 4.2.x
> >>> Even when not backwards compatible
> >>>
> >>> Fabian
> >>>
> >>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
> >> j...@nanthrax.net>
> >>> wrote:
> >>>
>  Hi guys,
> 
>  I would like to propose new wording in some Karaf designs:
> 
>  - In Karaf runtime, I would like to rename master/slave to
>  primary/secondary
>  - in Cellar, I would like to rename blacklist/whitelist to
> >> allowlist and
>  deny list
> 
>  Thoughts ?
> 
>  Regards
>  JB
> >>
> >>
>
>

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

We can rename the branch anyway.

I guess they gonna change the "default" soon.

Regards
JB

> Le 27 juil. 2020 à 16:06, Grzegorz Grzybek  a écrit :
> 
> Isn't "master" hardcoded in `git` binary - when you create an empty git
> repo?
> 
> $ cd /data/tmp/
> $ mkdir x
> $ cd x
> $ git init
> Initialized empty Git repository in /data/tmp/x/.git/
> $ git branch -vv
> $ git commit --allow-empty -m 'Initial commit'
> [master (root-commit) f402a8e] Initial commit
> $ git branch -vv
> * master f402a8e Initial commit
> 
> regards
> Grzegorz Grzybek
> 
> pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre  napisał(a):
> 
>> It sounds good, main is fine.
>> 
>> I will do the rename and update documentation/website.
>> 
>> Regards
>> JB
>> 
>>> Le 27 juil. 2020 à 14:55, Francois Papon 
>> a écrit :
>>> 
>>> May be we could use the new github default branch name "main".
>>> 
>>> regards,
>>> 
>>> François
>>> fpa...@apache.org
>>> 
>>> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
 Yes, I forgot to mention this. I was about to propose develop branch
>> instead of master branch.
 
 Regards
 JB
 
> Le 27 juil. 2020 à 14:37, Francois Papon 
>> a écrit :
> 
> Should we also rename "master" branch on git?
> 
> regards,
> 
> François
> fpa...@apache.org
> 
> Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
>> +1
>> 
>> and wherever it fits best.
>> Make sure the documentation is aligned, and maybe we could give hints
>> in
>> the current documentation already?
>> 
>> regards, Achim
>> 
>> 
>> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
>> lange.fab...@gmail.com>:
>> 
>>> +1
>>> 
>>> as a user of karaf 4.2 building our own distribution, we would be
>> okay with
>>> this being even in 4.2.x
>>> Even when not backwards compatible
>>> 
>>> Fabian
>>> 
>>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
>> j...@nanthrax.net>
>>> wrote:
>>> 
 Hi guys,
 
 I would like to propose new wording in some Karaf designs:
 
 - In Karaf runtime, I would like to rename master/slave to
 primary/secondary
 - in Cellar, I would like to rename blacklist/whitelist to
>> allowlist and
 deny list
 
 Thoughts ?
 
 Regards
 JB
>> 
>> 

Re: [PROPOSAL] Renaming terms

[Grzegorz Grzybek]

Isn't "master" hardcoded in `git` binary - when you create an empty git
repo?

$ cd /data/tmp/
$ mkdir x
$ cd x
$ git init
Initialized empty Git repository in /data/tmp/x/.git/
$ git branch -vv
$ git commit --allow-empty -m 'Initial commit'
[master (root-commit) f402a8e] Initial commit
$ git branch -vv
* master f402a8e Initial commit

regards
Grzegorz Grzybek

pon., 27 lip 2020 o 15:21 Jean-Baptiste Onofre  napisał(a):

> It sounds good, main is fine.
>
> I will do the rename and update documentation/website.
>
> Regards
> JB
>
> > Le 27 juil. 2020 à 14:55, Francois Papon 
> a écrit :
> >
> > May be we could use the new github default branch name "main".
> >
> > regards,
> >
> > François
> > fpa...@apache.org
> >
> > Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
> >> Yes, I forgot to mention this. I was about to propose develop branch
> instead of master branch.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 27 juil. 2020 à 14:37, Francois Papon 
> a écrit :
> >>>
> >>> Should we also rename "master" branch on git?
> >>>
> >>> regards,
> >>>
> >>> François
> >>> fpa...@apache.org
> >>>
> >>> Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
>  +1
> 
>  and wherever it fits best.
>  Make sure the documentation is aligned, and maybe we could give hints
> in
>  the current documentation already?
> 
>  regards, Achim
> 
> 
>  Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
>  lange.fab...@gmail.com>:
> 
> > +1
> >
> > as a user of karaf 4.2 building our own distribution, we would be
> okay with
> > this being even in 4.2.x
> > Even when not backwards compatible
> >
> > Fabian
> >
> > On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre <
> j...@nanthrax.net>
> > wrote:
> >
> >> Hi guys,
> >>
> >> I would like to propose new wording in some Karaf designs:
> >>
> >> - In Karaf runtime, I would like to rename master/slave to
> >> primary/secondary
> >> - in Cellar, I would like to rename blacklist/whitelist to
> allowlist and
> >> deny list
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
>
>

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

It sounds good, main is fine.

I will do the rename and update documentation/website.

Regards
JB

> Le 27 juil. 2020 à 14:55, Francois Papon  a 
> écrit :
> 
> May be we could use the new github default branch name "main".
> 
> regards,
> 
> François
> fpa...@apache.org
> 
> Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
>> Yes, I forgot to mention this. I was about to propose develop branch instead 
>> of master branch.
>> 
>> Regards
>> JB
>> 
>>> Le 27 juil. 2020 à 14:37, Francois Papon  a 
>>> écrit :
>>> 
>>> Should we also rename "master" branch on git?
>>> 
>>> regards,
>>> 
>>> François
>>> fpa...@apache.org
>>> 
>>> Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
 +1
 
 and wherever it fits best.
 Make sure the documentation is aligned, and maybe we could give hints in
 the current documentation already?
 
 regards, Achim
 
 
 Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
 lange.fab...@gmail.com>:
 
> +1
> 
> as a user of karaf 4.2 building our own distribution, we would be okay 
> with
> this being even in 4.2.x
> Even when not backwards compatible
> 
> Fabian
> 
> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
> wrote:
> 
>> Hi guys,
>> 
>> I would like to propose new wording in some Karaf designs:
>> 
>> - In Karaf runtime, I would like to rename master/slave to
>> primary/secondary
>> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
>> deny list
>> 
>> Thoughts ?
>> 
>> Regards
>> JB

Re: [PROPOSAL] Renaming terms

[Freeman Fang]

+1
Thanks JB!
Freeman

On Mon, Jul 27, 2020 at 2:22 AM Jean-Baptiste Onofre 
wrote:

> Hi guys,
>
> I would like to propose new wording in some Karaf designs:
>
> - In Karaf runtime, I would like to rename master/slave to
> primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> deny list
>
> Thoughts ?
>
> Regards
> JB

Re: [PROPOSAL] Renaming terms

[Francois Papon]

May be we could use the new github default branch name "main".

regards,

François
fpa...@apache.org

Le 27/07/2020 à 14:52, Jean-Baptiste Onofre a écrit :
> Yes, I forgot to mention this. I was about to propose develop branch instead 
> of master branch.
>
> Regards
> JB
>
>> Le 27 juil. 2020 à 14:37, Francois Papon  a 
>> écrit :
>>
>> Should we also rename "master" branch on git?
>>
>> regards,
>>
>> François
>> fpa...@apache.org
>>
>> Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
>>> +1
>>>
>>> and wherever it fits best.
>>> Make sure the documentation is aligned, and maybe we could give hints in
>>> the current documentation already?
>>>
>>> regards, Achim
>>>
>>>
>>> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
>>> lange.fab...@gmail.com>:
>>>
 +1

 as a user of karaf 4.2 building our own distribution, we would be okay with
 this being even in 4.2.x
 Even when not backwards compatible

 Fabian

 On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
 wrote:

> Hi guys,
>
> I would like to propose new wording in some Karaf designs:
>
> - In Karaf runtime, I would like to rename master/slave to
> primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> deny list
>
> Thoughts ?
>
> Regards
> JB

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

Yes, I forgot to mention this. I was about to propose develop branch instead of 
master branch.

Regards
JB

> Le 27 juil. 2020 à 14:37, Francois Papon  a 
> écrit :
> 
> Should we also rename "master" branch on git?
> 
> regards,
> 
> François
> fpa...@apache.org
> 
> Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
>> +1
>> 
>> and wherever it fits best.
>> Make sure the documentation is aligned, and maybe we could give hints in
>> the current documentation already?
>> 
>> regards, Achim
>> 
>> 
>> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
>> lange.fab...@gmail.com>:
>> 
>>> +1
>>> 
>>> as a user of karaf 4.2 building our own distribution, we would be okay with
>>> this being even in 4.2.x
>>> Even when not backwards compatible
>>> 
>>> Fabian
>>> 
>>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
>>> wrote:
>>> 
 Hi guys,
 
 I would like to propose new wording in some Karaf designs:
 
 - In Karaf runtime, I would like to rename master/slave to
 primary/secondary
 - in Cellar, I would like to rename blacklist/whitelist to allowlist and
 deny list
 
 Thoughts ?
 
 Regards
 JB
>> 

Re: [PROPOSAL] Renaming terms

[Francois Papon]

Should we also rename "master" branch on git?

regards,

François
fpa...@apache.org

Le 27/07/2020 à 13:57, Achim Nierbeck a écrit :
> +1
>
> and wherever it fits best.
> Make sure the documentation is aligned, and maybe we could give hints in
> the current documentation already?
>
> regards, Achim
>
>
> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> lange.fab...@gmail.com>:
>
>> +1
>>
>> as a user of karaf 4.2 building our own distribution, we would be okay with
>> this being even in 4.2.x
>> Even when not backwards compatible
>>
>> Fabian
>>
>> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
>> wrote:
>>
>>> Hi guys,
>>>
>>> I would like to propose new wording in some Karaf designs:
>>>
>>> - In Karaf runtime, I would like to rename master/slave to
>>> primary/secondary
>>> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
>>> deny list
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> JB
>

Re: [PROPOSAL] Renaming terms

[Jamie G.]

+1

Cheers,
Jamie

On Mon, Jul 27, 2020 at 9:27 AM Achim Nierbeck
 wrote:
>
> +1
>
> and wherever it fits best.
> Make sure the documentation is aligned, and maybe we could give hints in
> the current documentation already?
>
> regards, Achim
>
>
> Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
> lange.fab...@gmail.com>:
>
> > +1
> >
> > as a user of karaf 4.2 building our own distribution, we would be okay with
> > this being even in 4.2.x
> > Even when not backwards compatible
> >
> > Fabian
> >
> > On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
> > wrote:
> >
> > > Hi guys,
> > >
> > > I would like to propose new wording in some Karaf designs:
> > >
> > > - In Karaf runtime, I would like to rename master/slave to
> > > primary/secondary
> > > - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> > > deny list
> > >
> > > Thoughts ?
> > >
> > > Regards
> > > JB
> >
>
>
> --
>
> Apache Member
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> blog 
> Co-Author of Apache Karaf Cookbook 

Re: [PROPOSAL] Renaming terms

[Achim Nierbeck]

+1

and wherever it fits best.
Make sure the documentation is aligned, and maybe we could give hints in
the current documentation already?

regards, Achim


Am Mo., 27. Juli 2020 um 09:37 Uhr schrieb Fabian Lange <
lange.fab...@gmail.com>:

> +1
>
> as a user of karaf 4.2 building our own distribution, we would be okay with
> this being even in 4.2.x
> Even when not backwards compatible
>
> Fabian
>
> On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
> wrote:
>
> > Hi guys,
> >
> > I would like to propose new wording in some Karaf designs:
> >
> > - In Karaf runtime, I would like to rename master/slave to
> > primary/secondary
> > - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> > deny list
> >
> > Thoughts ?
> >
> > Regards
> > JB
>


-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Re: [PROPOSAL] Renaming terms

[Fabian Lange]

+1

as a user of karaf 4.2 building our own distribution, we would be okay with
this being even in 4.2.x
Even when not backwards compatible

Fabian

On Mon, Jul 27, 2020 at 8:22 AM Jean-Baptiste Onofre 
wrote:

> Hi guys,
>
> I would like to propose new wording in some Karaf designs:
>
> - In Karaf runtime, I would like to rename master/slave to
> primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> deny list
>
> Thoughts ?
>
> Regards
> JB

Re: [PROPOSAL] Renaming terms

[Francois Papon]

+1

regards,

François
fpa...@apache.org

Le 27/07/2020 à 08:21, Jean-Baptiste Onofre a écrit :
> Hi guys,
>
> I would like to propose new wording in some Karaf designs:
>
> - In Karaf runtime, I would like to rename master/slave to primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and deny 
> list
>
> Thoughts ?
>
> Regards
> JB

Re: Migration to ci-builds.a.o

[Francois Papon]

Hi,

I asked to INFRA for the installation of the missing Github PR builder
plugin to add PR jobs.

regards,

François
fpa...@apache.org

Le 27/07/2020 à 08:18, Jean-Baptiste Onofre a écrit :
> Hi everyone,
>
> Our main builds have moved to a new CI (ci-builds.apache.org 
> ):
>
> - karaf-runtime-master
> - karaf-runtime-4.2.x
> - karaf-runtime-4.1.x (that will be removed in couple of hours)
> - karaf-decanter-master
> - karaf-cellar-master
> - karaf-cave-master
>
> I’m preparing the PR builds for our different projects.
>
> I will keep you posted soon.
>
> Regards
> JB

Re: [PROPOSAL] Renaming terms

[Grzegorz Grzybek]

+1

JBO - there will be XSDs to change:
 -
https://github.com/apache/karaf/blob/master/features/core/src/main/java/org/apache/karaf/features/internal/model/processing/FeaturesProcessing.java#L71-L83
 -
https://github.com/apache/karaf/blob/master/features/core/src/main/resources/org/apache/karaf/features/karaf-features-processing-1.0.0.xsd#L37-L39

regards
Grzegorz Grzybek

pon., 27 lip 2020 o 08:45 Jean-Baptiste Onofre  napisał(a):

> Hi,
>
> I would like to use the next major release to do the change (4.3.0), as
> it’s not really backward compatible.
>
> Regards
> JB
>
> > Le 27 juil. 2020 à 08:44, Serge Huber  a écrit :
> >
> > +1, I've also been looking at this for Apache Unomi.
> >
> > Will you do this in minor or major updates?
> >
> > Regards,
> >  Serge...
> >
> >
> > On Mon, Jul 27, 2020 at 8:21 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi guys,
> >>
> >> I would like to propose new wording in some Karaf designs:
> >>
> >> - In Karaf runtime, I would like to rename master/slave to
> >> primary/secondary
> >> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> >> deny list
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
>
>

Re: [PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

Hi,

I would like to use the next major release to do the change (4.3.0), as it’s 
not really backward compatible.

Regards
JB

> Le 27 juil. 2020 à 08:44, Serge Huber  a écrit :
> 
> +1, I've also been looking at this for Apache Unomi.
> 
> Will you do this in minor or major updates?
> 
> Regards,
>  Serge...
> 
> 
> On Mon, Jul 27, 2020 at 8:21 AM Jean-Baptiste Onofre 
> wrote:
> 
>> Hi guys,
>> 
>> I would like to propose new wording in some Karaf designs:
>> 
>> - In Karaf runtime, I would like to rename master/slave to
>> primary/secondary
>> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
>> deny list
>> 
>> Thoughts ?
>> 
>> Regards
>> JB

Re: [PROPOSAL] Renaming terms

[Serge Huber]

+1, I've also been looking at this for Apache Unomi.

Will you do this in minor or major updates?

Regards,
  Serge...


On Mon, Jul 27, 2020 at 8:21 AM Jean-Baptiste Onofre 
wrote:

> Hi guys,
>
> I would like to propose new wording in some Karaf designs:
>
> - In Karaf runtime, I would like to rename master/slave to
> primary/secondary
> - in Cellar, I would like to rename blacklist/whitelist to allowlist and
> deny list
>
> Thoughts ?
>
> Regards
> JB

[PROPOSAL] Renaming terms

[Jean-Baptiste Onofre]

Hi guys,

I would like to propose new wording in some Karaf designs:

- In Karaf runtime, I would like to rename master/slave to primary/secondary
- in Cellar, I would like to rename blacklist/whitelist to allowlist and deny 
list

Thoughts ?

Regards
JB

Migration to ci-builds.a.o

[Jean-Baptiste Onofre]

Hi everyone,

Our main builds have moved to a new CI (ci-builds.apache.org 
):

- karaf-runtime-master
- karaf-runtime-4.2.x
- karaf-runtime-4.1.x (that will be removed in couple of hours)
- karaf-decanter-master
- karaf-cellar-master
- karaf-cave-master

I’m preparing the PR builds for our different projects.

I will keep you posted soon.

Regards
JB