I agree also on removing the master branch. As a relatively new member of the community it's been a source of confusion to me when looking at what is said in the wiki about it (https://cwiki.apache.org/confluence/display/GEODE/Versioning+and+Branching) and comparing it with the actual practice.
Alberto G. ________________________________ From: Jacob Barrett <jabarr...@vmware.com> Sent: Friday, June 26, 2020 5:26 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: Fate of master branch I am 100% in favor or dropping the master branch completely. I felt like it was always a source of confusion. Was it the most recent release or the latest version number. I know we have had issues with even correctly merging the latest version back into it sometimes. I really can’t see any reason for keeping it around. -Jake > On Jun 26, 2020, at 8:05 AM, Blake Bender <bbl...@vmware.com> wrote: > > Apologies if this has been addressed already and I missed it. In keeping > with other OSS projects, I believe it’s time we did something about removing > the insensitive term master from Geode repositories. > > One choice a lot of projects appear to be going with is a simple rename from > master • main. In our own case, however, master isn’t really in use for > anything vital. We track releases with a tag and a branch to backport fixes > to, and the develop branch is the “source of truth” latest-and-greatest > version of the code. We could thus simply delete master with no loss I’m > aware of. Any opinions? > > Thanks, > > Blake >
