On Thu, 3 Oct 2019 at 14:13, Vladimir Sitnikov <[email protected]> wrote: > > >Enough for what? > > For the project.
I still don't follow. > > Current tag names are like > v4_0_RC7 > v5_0_RC1 > v5_0_RC2 > v5_1_1_RC1 > v5_1_RC1 > v5_1_RC2 > > They do not follow the new "rel/*" naming So? The rel/* naming is intended for releases, not RCs Such tags are protected and cannot be deleted (easily). > so we need to invent the way we would tag upcoming releases. Does not follow, as the rel/* naming is not intended for RCs or other tags that may not be permanent. We can continue to use the tag names as above. However they must not be created under rel/ Unfortunately GitHub seems to think that every tag is a release. I would be great if there was a way to suppress that behaviour, so RC tags were not treated as releases by GitHub. I don't know if there is a naming convention that would make it clear that the RC tags are temporary. If so, it might be worth changing the RC tag name convention. Otherwise, I don't see any point. At present, only release tags ought to be given different names, i.e. with a rel/ prefix. > Vladimir
