Re: Re: Public Tags of Releases

Hi, I agree that tags should be treated as immutable, because that's what distinguishes them from branches. That's true of any VCS, but git has the added restriction that they're treated as global: tags from different remotes aren't tracked separately, they are all merged into the local namespace immediately. On 28 November 2017 17:16:52 GMT+00:00, Sara Golemon <pollita@php.net> wrote: >Okay, that's a reasonable middle ground. We could tag as >php-X.Y.Z-something Tuesday, then tag again as php-X.Y.Z on Thursday. >That would only add one step to the release process at the minor cost >of having more tags. *shrug* The logical name for this would be "php-X.Y.Z-RC1": this is a Candidate revision which we believe is going to be tagged as Release. However, the current process abuses that term for late-stage test builds which are not actually release candidates. :( Another alternative would be to simply increment the build number on the rare occasions a tag is withdrawn: if 7.2.2 was a bad tag, just release 7.2.3 instead. Regards, -- Rowan Collins [IMSoP]