Re: naming development branches consistently

Considering the project currently follows the trunk-based development workflow, I am +1 for trunk In general I am fine also with main, but trunk sounds more accurate to me personally. On Wed, 26 Aug 2020 at 4:03, Benjamin Lerer wrote: > +1 for trunk or main (slight preference for trunk) > > > >

Re: naming development branches consistently

+1 for trunk or main (slight preference for trunk) On Tue, Aug 25, 2020 at 8:52 PM Mick Semb Wever wrote: > +1 for trunk and main. > > Thanks for raising this Brandon. > > > > On Tue, 25 Aug 2020 at 20:40, Cyril Scetbon wrote: > > > Scott, I don’t think it does and don’t see any offense in wh

Re: naming development branches consistently

+1 for trunk and main. Thanks for raising this Brandon. On Tue, 25 Aug 2020 at 20:40, Cyril Scetbon wrote: > Scott, I don’t think it does and don’t see any offense in what I’ve said. > Can you be more specific instead of sending a link with rules numbers that > I don’t think apply ? I can als

Re: naming development branches consistently

Scott, I don’t think it does and don’t see any offense in what I’ve said. Can you be more specific instead of sending a link with rules numbers that I don’t think apply ? I can also send links to definitions of all the words in the rules you sent but it could be a waste of time. We can continue

Re: naming development branches consistently

Cyril, your commentary violates the code of conduct of the ASF re rules #2 and #5. It could also be very hurtful to those who feel this is important, as many in the community do. Please think before pushing further on this as projects need to be

Re: naming development branches consistently

Wow, thanks for the link Almero. I suppose the dictionary comes next then 🤷‍♂️ > On Aug 24, 2020, at 6:54 PM, Gouws, Almero wrote: > > https://www.zdnet.com/article/mysql-drops-master-slave-and-blacklist-whitelist-terminology/ > > -Almero > > -Original Message- > From: Cyril Scetbon

Re: naming development branches consistently

Just saw it’s actually a thing https://github.com/github/renaming … > On Aug 24, 2020, at 6:47 PM, Cyril Scetbon wrote: > > Seriously ? Should we change how MySQL architectures are defined ? Should we > remove it from the dictionary too ? Just to see how ra

RE: naming development branches consistently

https://www.zdnet.com/article/mysql-drops-master-slave-and-blacklist-whitelist-terminology/ -Almero -Original Message- From: Cyril Scetbon Sent: Monday, August 24, 2020 3:47 PM To: dev@cassandra.apache.org Subject: RE: [EXTERNAL] naming development branches consistently CAUTION: This e

Re: naming development branches consistently

Seriously ? Should we change how MySQL architectures are defined ? Should we remove it from the dictionary too ? Just to see how radical It could be … 🤦‍♂️ > On Aug 24, 2020, at 12:12 PM, Brandon Williams wrote: > > With the current social climate I thought removing the master > reference rath

Re: naming development branches consistently

+1 to trunk and main > On Aug 24, 2020, at 9:59 AM, Brandon Williams wrote: > > I'm fine with that, though it's probably a tab bit more involved than > the rest due to website/doc changes. > > On Mon, Aug 24, 2020 at 11:29 AM Aleksey Yeshchenko > wrote: >> >> Last thing I want is to bikeshed,

Re: naming development branches consistently

I'm fine with that, though it's probably a tab bit more involved than the rest due to website/doc changes. On Mon, Aug 24, 2020 at 11:29 AM Aleksey Yeshchenko wrote: > > Last thing I want is to bikeshed, but seems like ‘main’ is what’s being > adopted by GitHub, so we might as well rename all ‘m

Re: naming development branches consistently

Last thing I want is to bikeshed, but seems like ‘main’ is what’s being adopted by GitHub, so we might as well rename all ‘master’ and ’trunk’ branches to that. > On 24 Aug 2020, at 17:22, Joshua McKenzie wrote: > > Ah! Totally didn't even think of that. Good point. > > On Mon, Aug 24, 2020 at

Re: naming development branches consistently

Ah! Totally didn't even think of that. Good point. On Mon, Aug 24, 2020 at 12:12 PM Brandon Williams wrote: > With the current social climate I thought removing the master > reference rather than proliferating it would be better. > > On Mon, Aug 24, 2020 at 11:07 AM Joshua McKenzie > wrote: > >

Re: naming development branches consistently

With the current social climate I thought removing the master reference rather than proliferating it would be better. On Mon, Aug 24, 2020 at 11:07 AM Joshua McKenzie wrote: > > Why not rename "trunk" to "master" in C*? =D > > On Mon, Aug 24, 2020 at 11:17 AM Brandon Williams wrote: > > > Hell

Re: naming development branches consistently

Why not rename "trunk" to "master" in C*? =D On Mon, Aug 24, 2020 at 11:17 AM Brandon Williams wrote: > Hello, > > Currently in the cassandra repo our development branch is named > 'trunk', but this is not consistently used in other repos, such as > cassandra-dtest, -builds, -website, and prob