I agree, I am not justifying the use of repository for small bug fixes etc. or short term individual tasks
I am justifying why PR clear has a feature branch in the geode repository. Regards Naba -----Original Message----- From: Jacob Barrett <jbarr...@amduat.net> Sent: Tuesday, June 2, 2020 4:48 PM To: dev@geode.apache.org Subject: Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches > On Jun 2, 2020, at 4:29 PM, Nabarun Nag <n...@vmware.com> wrote: > > - We are maintaining feature/GEODE-7665 which is the feature branch for PR > clear work on which multiple developers are working on. > - We are maintaining this in Geode repository. > - All sub-tasks of GEODE-7665 are merged into this feature branch. > - Anyone in the Geode community can work on any subtask > - This is a long running, and a massive feature development which is > manipulating core code on Apache Geode. Hence all work is pushed to the > feature branch to keep develop isolated from a regression introduced in PR > clear work. > - We have previously used release flags for Lucene work which we found to be > inefficient and unnecessary extra work. > > We vote that PR clear feature branch be maintained in the Geode Repository as > this is a long running, massive effort involving everyone from the community. > > When the PR clear tasks are completed, the branch will be rigorously tested > and then squash merged into develop and the feature branch will be deleted. I think there can always be exceptions for any rule. I can even understand the desire to have long running branches for large scale refactors or features maintained centrally. The issue is the most of the branches are not of this exceptional scale. I want to eliminate this clutter and consider exceptions where it makes sense. Perhaps which we could ask the ASF to have its bots ignore specifically prefixed branches to future reduce the noise produced by using the Geode repo in these exceptional cases. -Jake
