Re: Clean up old and obsolete branches

@Marc, I like this idea. However, some folks believe it might be useful to use the official repo to work in groups (group of committers). I did not want to push this without a broader discussion; that is why I am proposing that people can use the official repository, as long as they remove the bran

Re: Clean up old and obsolete branches

any workable procedure (including yours, Rafael) will do but let's be extremely patient and lenient. I think we can start deleting a lot of old branches (RC-branches and merged PRs to start with) On Mon, Dec 18, 2017 at 2:23 PM, Marc-Aurèle Brothier wrote: > +1 for me > > On the point 5, since y

Re: Clean up old and obsolete branches

+1 for me On the point 5, since you can have people working together on forks, I would simply state that no other branches except the official ones can be in the project repository, removing: "If one uses the official repository, the branch used must be cleaned right after merging;" On Mon, Dec 1

Re: Clean up old and obsolete branches

Guys, this is the moment to give your opinion here. Since nobody has commented anything on the protocol. I will just add some more steps before deletion. 1. Only maintain the master and major release branches. We currently have a system of X.Y.Z.S. I define major release here as a release th

Re: Clean up old and obsolete branches

sounds lime a lazy consensus vote; +1 from me On Thu, Dec 14, 2017 at 7:07 PM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > Guys, > > Khosrow has done a great job here, but we still need to move this forward > and create a standard/guidelines on how to use the official repo. Looking

Re: Clean up old and obsolete branches

Guys, Khosrow has done a great job here, but we still need to move this forward and create a standard/guidelines on how to use the official repo. Looking at the list in [1] we can clearly see that things are messy. This is a minor discussion, but in my opinion, we should finish it. [1] https://i

Re: Clean up old and obsolete branches

I agree Erik. I updated the list in CLOUDSTACK-10169 with more information (last updated, last commit, HEAD on master and PR status/number) to give us more immediate visibility of the status of those branches. So any branches can be deleted if: - which its HEAD exists on master - its PR was merged

Re: Clean up old and obsolete branches

I thought someone might bring that up. The problem with using branches in the official repo is that only committers will be able to commit there. So, we would restrict the group of people that might be able to participate in this type of cooperation. I do not see the difficulty for a contributor/co

Re: Clean up old and obsolete branches

On Thu, Nov 30, 2017 at 9:05 PM, Khosrow Moossavi wrote: > Hi Community > > I would like to start the discussion around deleting old and obsolete > branches on github repository. This will help newcomers (including myself) > to keep track of which branches are important and which are not. And sinc

Re: Clean up old and obsolete branches

> Op 3 december 2017 om 12:54 schreef Rafael Weingärtner > : > > > I agree with everything Khosrow said. Additionally, the branches CID can > be deleted, they are branches referencing problems found/pointed out by > Coverity scans. These Coverity problems are enumerated as CID-X. > https:/

Re: Clean up old and obsolete branches

I agree with everything Khosrow said. Additionally, the branches CID can be deleted, they are branches referencing problems found/pointed out by Coverity scans. These Coverity problems are enumerated as CID-X. https://scan6.coverity.com/reports.htm#v39957/p10672 I have one extra thing to comm

Re: Clean up old and obsolete branches

@Daan That's a good point, I'll try to update the list to CLOUDSTACK- wherever applicable. But the majority of branches are 4.1.x to 4.6.x, which might be able to be cleaned up easily. - I feel we might be able to delete everything 4.1.x, 4.2.x, 4.3.x, 4.4.x, 4.5.x, 4.6.x (almost blindly). - the o

Re: Clean up old and obsolete branches

also I think we can tolerate collective work on our repo. Not everything has to go on forks. On Fri, Dec 1, 2017 at 11:04 AM, Daan Hoogland wrote: > Rafael, I don't think that works. the versions in the pom.xml files are > updated to non snapshot versions on per release mini branches. I like the

Re: Clean up old and obsolete branches

Rafael, I don't think that works. the versions in the pom.xml files are updated to non snapshot versions on per release mini branches. I like the principle but be carefull not to remove the GA branches. On Fri, Dec 1, 2017 at 10:41 AM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > Th

Re: Clean up old and obsolete branches

Thanks for the initiative and the hard worki Khosrow! In my opinion, we should only maintain the master and major release branches. Then, for minor versions, we can keep track of them using tags. There is no need to have things such as GA-4.4.1, GA-4.4.2, and so forth. Instead, we should keep only

Re: Clean up old and obsolete branches

thanks for that list Khosrow, Also very usefull for cleaning people to clean their own fork. I think you can start with the lowest pom versions but I changed one because the referred ticket isn't closed. It's my own and I'll have a look later today. For a lot of the branches the ticket aren't clea

Re: Clean up old and obsolete branches

Thanks for the initiative, Khosrow. +1 on removing obsolete branches. 2017-11-30 18:05 GMT-02:00 Khosrow Moossavi : > Hi Community > > I would like to start the discussion around deleting old and obsolete > branches on github repository. This will help newcomers (including myself) > to keep trac