+1
On Wed, Jul 22, 2020 at 2:34 PM Ravishankar N
wrote:
> Hi,
>
> The gluster code base has some words and terminology (blacklist,
> whitelist, master, slave etc.) that can be considered hurtful/offensive
> to people in a global open source setting. Some of words can be fixed
> trivially but the
Hi,
The Gluster community is pleased to announce the release of Gluster7.7
(packages available at [1]).
Release notes for the release can be found at [2].
Major changes, features and limitations addressed in this release:
None
Please Note: Some of the packages are unavailable and we are working
+1
> On 22-Jul-2020, at 2:34 PM, Ravishankar N wrote:
>
> Hi,
>
> The gluster code base has some words and terminology (blacklist, whitelist,
> master, slave etc.) that can be considered hurtful/offensive to people in a
> global open source setting. Some of words can be fixed trivially but th
On Wed, Jul 22, 2020 at 12:37 PM Shwetha Acharya
wrote:
>
> 1. Can I replace master:slave with primary:secondary everywhere in the
>> code and the CLI? Are there any suggestions for more appropriate
>> terminology?
>>
> Primary and Secondary sounds good.
>
ACK, though others use leader and follo
On Wed, Jul 22, 2020 at 2:34 PM Ravishankar N
wrote:
> Hi,
>
> The gluster code base has some words and terminology (blacklist,
> whitelist, master, slave etc.) that can be considered hurtful/offensive
> to people in a global open source setting. Some of words can be fixed
> trivially but the Geo
Hi,
so finally, after several hours of debugging (some DNS problem), we
ironed the last problem with automated AWS install of Jenkins builder,
and our news freshly installed c7 finished a regular regression run
today:
https://build.gluster.org/job/centos7-regression/10520/consoleFull
We are going
> 1. Can I replace master:slave with primary:secondary everywhere in the
> code and the CLI? Are there any suggestions for more appropriate
> terminology?
>
Primary and Secondary sounds good.
>
> 2. Is it okay to target the changes to a major release (release-9) and
> *not* provide backward compat
1. Can I replace master:slave with primary:secondary everywhere in the
code and the CLI? Are there any suggestions for more appropriate
terminology?
>> Other options could be - Leader : follower
2. Is it okay to target the changes to a major release (release-9) and
*not* provide backward co
+1 for this.
On Wed, Jul 22, 2020 at 10:04 AM Ravishankar N wrote:
>
> Hi,
>
> The gluster code base has some words and terminology (blacklist,
> whitelist, master, slave etc.) that can be considered hurtful/offensive
> to people in a global open source setting. Some of words can be fixed
> triv
Hi,
The gluster code base has some words and terminology (blacklist,
whitelist, master, slave etc.) that can be considered hurtful/offensive
to people in a global open source setting. Some of words can be fixed
trivially but the Geo-replication code seems to be something that needs
extensive
10 matches
Mail list logo
