Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101194 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82655 invoked from network); 29 Nov 2017 00:30:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Nov 2017 00:30:56 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.54 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 74.125.83.54 mail-pg0-f54.google.com Received: from [74.125.83.54] ([74.125.83.54:39967] helo=mail-pg0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/E2-57104-FBFFD1A5 for ; Tue, 28 Nov 2017 19:30:55 -0500 Received: by mail-pg0-f54.google.com with SMTP id k15so700634pgr.7 for ; Tue, 28 Nov 2017 16:30:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=KKTQLaKRhu6U8IaTJGLBZOXXd+DjLZulV1bQHfLbzCc=; b=B8UtG+e+m/xyoay2n0zWDBUtIOkd8k9l5v7axf7IdIQH0ivDBb5Vg91pO014pfMNni HqjJ+KzGpfEzJTQb7Ir5txVD1ZfESs+ea8/APoQnmAyQgcfYrG9cp6B3b0hYay20sYJv an3uMuN5UNGIipZJzBKPK0oxkyIShpQfXbxELRnYLW6ir1pCNQykJlLIS/qYNzLj+WuG 5oYNy0gxrJexTIf3JGzh2j8NvKzxFBW/ZwriXGjl5iRvoncsacvua5RqFts3sXsC8wKl YGqbadr18H/1jG5gI0Bansuu3tZT4gVtg+iANUqHInLx7hIOPrAODEaL6eSUsDjGJAGg ytIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=KKTQLaKRhu6U8IaTJGLBZOXXd+DjLZulV1bQHfLbzCc=; b=CerxL1qbIC0ksXYsgEDyRpA/xRnSf2OYGFVqMUeyOxZjYe4t9t/TyQY7pT7lVFOmBW LUFeopI+q78Zq/FmqCKY2oOjBjG9g1n+6UYb4OYou8KlYG7CaC3ePnVlNg9g/Dljm7go YR2VJklf+pTroQxRxOucm5ZyJrA8hqiETeweMpr4NDeZSc/QTdNduveiyKKksWjaWoZG 8j/I84a5j3++LE59awsIPsgjPe6srgCtrCOdjyAD6x+VzcTeByYpRAArQRtOC5eMUcl5 VTRbrdxIBfQ38+hUILiLWiqEg6QYBOZ4RcwRqfmqK9zsOFwpdxkJ18BlQUwt2+M5Wii1 7VkA== X-Gm-Message-State: AJaThX6FKYFBAHVTuYcsh7R2VpWMZuS+QrobWITzfKEgGdbPffSg60Sj wQdLZM836gXRMQr+XFj6BQ== X-Google-Smtp-Source: AGs4zMZOKUFHQxpVyncWujVZ2Grs6cBY2nAPOkKq/z2Od+NJ3k6Cyde+UZifaxLTqZRjQkQgfRoPyg== X-Received: by 10.98.157.67 with SMTP id i64mr1058250pfd.40.1511915451881; Tue, 28 Nov 2017 16:30:51 -0800 (PST) Received: from Stas-Pro-2016.local ([65.246.71.93]) by smtp.gmail.com with ESMTPSA id m63sm364112pfj.80.2017.11.28.16.30.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Nov 2017 16:30:51 -0800 (PST) To: Niklas Keller , PHP Internals , Sara Golemon , Joe Watkins , Remi Collet , Anatol Belski References: Message-ID: <8888326c-553e-3d57-1077-8f23a66d371c@gmail.com> Date: Tue, 28 Nov 2017 16:30:49 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Public Tags of Releases From: smalyshev@gmail.com (Stanislav Malyshev) 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 smalyshev@gmail.com