sebb> The 5.2-SNAPSHOT builds will hang around unless manually deleted It will be superseded by CI automatically as soon as the vote passes and the version is incremented to 5.2-SNAPSHOT.
1) As far as I read the discussion, no-one really cares of the past tags, so I'm fine with just leaving tag placement "as is". 2) I'm inclined to drop docs/ folder from the source repository. It should better be placed to the separate site repository. 3) I'm inclined to drop "test-bin" and "testhead" tags. The sad thing with "testhead" is that tag has its own "root commit" somehow. Those tags are not important anyway. Then docs-x.y branches are pretty-much harmless. The only annoying thing is the number of the branches, however it is manageable. Here's the preview repo: https://github.com/vlsi/jmeter-git-cleanup-result There's consistency issue with branch and tag naming. For instance: rel-2_0_0 rel-2_1 doc-v2_3_1 docs-2.4 docs-5.1 tags/v5_1 Frankly speaking, I would prefer to name release branches as release-$VERSION, and name tags as v$VERSION. For instance: release-5.1 branch and v5.1 tag. Of course we can't just rename old tags (since people might rely on that naming), however we could create v5.1 kind of tags for each v5_1, and we can use v5.2, and so on later. What do you think? "docs-" branch name is misleading, as it effectively used as a release branch for a specific version. Vladimir
