Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101180
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.161 cause and error)
MIME-Version: 1.0
Date: Tue, 28 Nov 2017 16:55:50 +0100
Message-ID: <CANUQDCgePs2B3JrYhWGA3rMW9OM0tmnRpdinPs8=Zkt_vHYDUA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>, Sara Golemon <pollita@php.net>, 
	Joe Watkins <pthreads@pthreads.org>, Remi Collet <remi@php.net>, Anatol Belski <ab@php.net>
Content-Type: multipart/alternative; boundary="089e0832c55c99dc18055f0d0dfb"
Subject: Public Tags of Releases
From: me@kelunik.com (Niklas Keller)

--089e0832c55c99dc18055f0d0dfb
Content-Type: text/plain; charset="UTF-8"

Morning,

it's the current practice to tag releases publicly two days before release
and then do the final QA phase. Could we please stop that?

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.

If there won't be a re-tag but a new tag name instead, there's no reason to
not see the tagging as release instead of the release announcement two days
later.

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
different tag or just a commit reference and the release announcement can
happen directly after the tagging.

Regards, Niklas

--089e0832c55c99dc18055f0d0dfb--