5 ms·
and if you do this you deserve to burn in a fiery pit for being a bad bad bad release manager If you tag a commit you better stick to your guns and never chang
by feld 11y ago
and if you do this you deserve to burn in a fiery pit for being a bad bad bad release manager
If you tag a commit you better stick to your guns and never change it. You can't just re-tag or re-roll your releases because you found a bug. Bugs happen. Increment your version number, cut/tag a new release, and move on. You will never have a perfect release. Ever.
- deleted 11y ago[deleted]
- TazeTSchnitzel 11y agoTagging a PHP release doesn't mean finalising it. That's when the tarballs go up and the email goes out.
- wtetzner 11y agoYes, but moving a tag is very bad. A tag is meant to be an immutable pointer into a repo. If you create a php-7.0.0 tag, and you find a bad bug, then make a new tag, either php-7.0.1, or since you might still want to call the release PHP 7.0.0, maybe name it php-7.0.0-bugfix1 or something.