Hi! > If there's a mistake that needs to be fixed and that's detected within > these two days, a re-tag needs to happen. If the old tag is deleted and a > new modified tag is published, all cloned Git repositories that already > received the old tag will keep the old tag and never receive the new tag > unless the old tag is manually removed first. That's problematic.
That's not how git is supposed to work? If you syncronize the repo you should get the new tag. If you cloned repo once and never update then of course you don't get new tag, but you also don't get the fix... > If tags are necessary for the final QA phase and the QA phase should happen > before release, then these tags shouldn't be public, but in a private > repository instead. If tags aren't necessary, then the QA phase can use a But we don't have private repository? We have security repo but this one is for security fixes and not for release work, in fact it doesn't even have to be up-to-date with release, it's only for keeping/exchanging security patches. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
