Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101183 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40580 invoked from network); 28 Nov 2017 16:26:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2017 16:26:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.162 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.162 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.162] ([81.169.146.162:28621] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/36-26862-E1E8D1A5 for ; Tue, 28 Nov 2017 11:26:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1511886363; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References: In-Reply-To:MIME-Version:X-RZG-CLASS-ID:X-RZG-AUTH:Accept-Language: Auto-Submitted:Cc:Date:From:Message-ID:References:Reply-To:Resent-Cc: Resent-Date:Resent-From:Resent-To:Sender:Subject:To: Content-Alternative:Content-Description:Content-Disposition: Content-Duration:Content-Features:Content-ID:Content-Language: Content-Location:Content-MD5:Content-Transfer-Encoding:Content-Type: MIME-Version; bh=8Iqwo1i3esGu8aF/LzUX8q1vS3HUViK2SanIGTrF/1M=; b=uOXsFNsWPBPq/vYACwyTPdgLpyT9ZdbM1s3cplO5ZhcBvYYO4ZAsivLli7AaVBub+b Lg/DzfFuVcLClRaMgzB8VFB99CYPWKHEE+9SedFSwSHxBRUPYQRo96ZcAoGEw9ePIhue /ECTExGfMX74+wIOefaFaUI6yIvZpYfmsw6FI= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mlsGbEv0XHBzMIJSS+jKTzde5mDb8AaBUcZiAscA== X-RZG-CLASS-ID: mo00 Received: by mail-yb0-f170.google.com with SMTP id c69so172814ybf.3 for ; Tue, 28 Nov 2017 08:26:03 -0800 (PST) X-Gm-Message-State: AJaThX6Fuwk5UTuYOfn74wHLe0RP2Vzl6qha0cnFMqK8NHTc/k7Tz6l3 I7hnojAvCSoYcptj+/560UzBaCPOCsXioACqlrI= X-Google-Smtp-Source: AGs4zMb7VkK0chP0v7uySAUHB6MNHKsZC0a6mIhy14nxhq33e1BOxVNQfjw1ljwvPdJW85ybZrKdBxpj5yIv5b98iMs= X-Received: by 10.37.97.149 with SMTP id v143mr26191257ybb.424.1511886363124; Tue, 28 Nov 2017 08:26:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.124.71 with HTTP; Tue, 28 Nov 2017 08:26:02 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Nov 2017 17:26:02 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Joe Watkins Cc: PHP internals , Sara Golemon , Remi Collet , Anatol Belski Content-Type: multipart/alternative; boundary="001a1142e7109d6d6a055f0d7971" Subject: Re: Public Tags of Releases From: me@kelunik.com (Niklas Keller) --001a1142e7109d6d6a055f0d7971 Content-Type: text/plain; charset="UTF-8" > > Afternoon, > > Tags are created in release branches, these branches should not be part of > any workflow other than our internal one. > I'm not talking about branches, but tags. Updating these release branches doesn't matter and is totally fine, as these are normal branches and thus not deemed immutable. It's problematic to tag other than publicly, anywhere we create these tags > is public and presumably would cause the same problem for those people who > choose to use release branches in their workflow. > > Cheers > Joe > Regards, Niklas --001a1142e7109d6d6a055f0d7971--