Since the branch proposed for deletion is the default branch in geode-examples, you will need to file an ASF INFRA ticket to change that default. This is a great discussion thread, but ASF will require a [VOTE] thread to be cited.
I am concerned about keeping it easy for someone who has just cloned geode to identify the most stable branch for their purpose. Before, they could always be assured `git checkout master` would give the flagship release. Now, new users will be immediately forced into some daunting detective work to sift through hundreds of haphazard tags and branches (a task even veteran committers frequently fail). I would strongly encourage an aggressive cleanup of unhelpful branches and tags, as Jacob proposed last month, before getting rid of the latest_release concept. On 7/7/20, 8:24 AM, "Blake Bender" <[email protected]> wrote: Just to follow up on this: I've filed GEODE-8335 (https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8335&data=02%7C01%7Conichols%40vmware.com%7Cb3a06863e89e4b9f06bb08d82289cebe%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637297322561614965&sdata=bXkoPZBLk3CR29lfV6AP5OcnjPWUvjuhSk3AZAXC7Do%3D&reserved=0) to track, respectfully (cowardly __ ) deferring to individuals who regularly contribute to the various Geode repos to handle it as they see fit. I'll take care of the several Geode Native associated repos. Thanks, Blake On 6/26/20, 12:21 PM, "Dave Barnes" <[email protected]> wrote: +1 if we can override git’s ‘master’ default and establish ‘develop’ in its place. Otherwise renaming to ‘main’ would solve the problem with the negative connotations. NB: Mark, I think the 3-vote convention is just for back-ports to the release-branch. I don’t think of it as applying to a general discussion like this one. > On Jun 26, 2020, at 9:42 AM, Anthony Baker <[email protected]> wrote: > > By just do it, I assume you mean: > > - Contact delete master where not needed > - Rename master to main when needed > - Contact INFRA to change the default branch > - Update README and CI jobs as needed > > Across *all* geode repos. > > > Anthony > > >> On Jun 26, 2020, at 9:38 AM, Mark Hanson <[email protected]> wrote: >> >> +1 to delete. No good reason to keep it that I know of. I think I am the third +1 with no -1s so just do it. >> >> Thanks, >> Mark >> >>> On Jun 26, 2020, at 9:13 AM, Alexander Murmann <[email protected]> wrote: >>> >>> +1 to deleting. Given we tag everything properly on the other branches, I >>> don't see the need for it either. >>> >>> On Fri, Jun 26, 2020 at 9:03 AM Alberto Bustamante Reyes >>> <[email protected]> wrote: >>> >>>> +1 for deleting master branch. An also for updating the wiki page about >>>> branching that Alberto pointed out. >>>> ________________________________ >>>> De: Bruce Schuchardt <[email protected]> >>>> Enviado: viernes, 26 de junio de 2020 17:37 >>>> Para: [email protected] <[email protected]> >>>> Asunto: Re: Fate of master branch >>>> >>>> Let's just delete it. I need to do that in my own repos as well. >>>> >>>> On 6/26/20, 8:05 AM, "Blake Bender" <[email protected]> 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 >>>> >>>> >>>> >> >
