Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F98F1879C for ; Wed, 13 Jan 2016 16:54:53 +0000 (UTC) Received: (qmail 82304 invoked by uid 500); 13 Jan 2016 16:54:52 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 82202 invoked by uid 500); 13 Jan 2016 16:54:52 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 82190 invoked by uid 99); 13 Jan 2016 16:54:52 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2016 16:54:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E2FBEC19B4 for ; Wed, 13 Jan 2016 16:54:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CeX2ESjZf_Oo for ; Wed, 13 Jan 2016 16:54:46 +0000 (UTC) Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 24A3131AD0 for ; Wed, 13 Jan 2016 16:54:46 +0000 (UTC) Received: by mail-wm0-f51.google.com with SMTP id u188so306175293wmu.1 for ; Wed, 13 Jan 2016 08:54:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OmnmebXG5xUl/gRiFkeJGeW3CI+xY1hLg/pOy+WH4rs=; b=JNdDSYbWBWlzf2jyT7iCK3r5Kx6eh6JI+iB39qpfCH1SCfno+EgoykOUcPre6RqZlT Kf4Nf49Rxu4b+aGnAH+kR4oM2dKBkT1PyVYJ246pL/DcXyDAvaQY++APXPvNCn03Xtj7 rau4NdXFfv67yesg8xY+SxZtAeWymJ9y0DXtuAhB9jE+WQcUwY5C1+uZvtKKNdmjZ5gG i/bKowDGbEdo2r4jkshH/MGyrK60dH3bV77bT0KFAHoEklftJMaBqQGv7KBjCAZ9G+K9 DSjfvYwSzulanYRzkGiYusUGpc3rOYz7+MZrqaGwxmJeQXw752Ts3lmw0dCw7ecDvWSh jrMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=OmnmebXG5xUl/gRiFkeJGeW3CI+xY1hLg/pOy+WH4rs=; b=bAXCetGzSJuVg0ynpLDGpYAr2brMRjqIvkTzDmAiDeye3yHn85PHIHoami/sODocuG b2kAwk0OX9q3dd1jsKljx3L/0KSYFo8hPsT7tiJliDT9r5s2cquNt8//AvXsZKzJkAPB NRRJsExfXQltNUUtPENFfIUnE7WIRtWTF2KlA7q3ATcYWUeVEkOD3lDdY4XgdqWfb7na u3XtlCdDBcThucG+j1P5/ka6xM38RkJqC0R9F9UtIbedk8ue8XdN+BHHzPJbfYGhFbNk 12loUz4B+WJnFQ0OLKNmt8ZtNq6IWzcrou0Usln9AHSuIRs3WBNeCEaVz6hyfTbX20fj qX4g== X-Gm-Message-State: ALoCoQkCFnAnrqRZKkq5tjuU1cyGNDuGBNyYK8c2aSbH07b1Id0jmySBDTVuEou3AU4tBl6E7cvubbBSSeqB6MuyOGvNG6pz6g== MIME-Version: 1.0 X-Received: by 10.194.241.228 with SMTP id wl4mr25583369wjc.11.1452704085838; Wed, 13 Jan 2016 08:54:45 -0800 (PST) Received: by 10.28.60.139 with HTTP; Wed, 13 Jan 2016 08:54:45 -0800 (PST) In-Reply-To: References: <528376755.3452141.1452667170372.JavaMail.yahoo@mail.yahoo.com> Date: Wed, 13 Jan 2016 08:54:45 -0800 Message-ID: Subject: Re: ASF git repository policy update From: Nick Dimiduk To: "dev@hbase.apache.org" Cc: "larsh@apache.org" Content-Type: multipart/alternative; boundary=089e01493c3200111a05293a0726 --089e01493c3200111a05293a0726 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ACK On Wednesday, January 13, 2016, Sean Busbey wrote: > no, definitely not. the "rel" space is reserved for PMC-approved releases= . > There's no foundation-backed need to preserve candidates that didn't get > approved. > > On Wed, Jan 13, 2016 at 9:32 AM, Nick Dimiduk > wrote: > > > Should we be pushing RC tags into the rel space as well as release tags= ? > > > > On Tuesday, January 12, 2016, > wrote: > > > > > +1 > > > > > > > > > From: Enis S=C3=B6ztutar > > > > > To: "dev@hbase.apache.org " < > dev@hbase.apache.org > > > > > > > Sent: Monday, January 11, 2016 11:17 AM > > > Subject: Re: ASF git repository policy update > > > > > > +1 on re-tagging releases under rel/ and using it going forward. > > > > > > Enis > > > > > > On Mon, Jan 11, 2016 at 11:05 AM, Sean Busbey > > > > wrote: > > > > > > > just to confirm, 'master' is no longer protected? > > > > > > > > On Mon, Jan 11, 2016 at 12:56 PM, Andrew Purtell < > apurtell@apache.org > > > > > > > > wrote: > > > > > > > > > Infa recently announced on infrastructure@ that, following > direction > > > > from > > > > > the Board, ASF git is now allowing force pushes and branch/tag > > deletion > > > > > again. In accordance with the guidance given by the Board there a= re > > > some > > > > > policy changes you should be aware of: > > > > > > > > > > - First, if a forced commit is pushed, the subsequent commit > email > > > to > > > > > commits@ will contain '[Forced Update!]' in the subject line. > The > > > > hope > > > > > here is that it draws extra attention to the situation for a > > project > > > > > community tobe aware, and take appropriate action if needed. > > > > > > > > > > - Second, the 'protected' Git ref-space is now refs/tags/rel/*= . > > Any > > > > > tags under rel/, can be assured to carry the complete immutabl= e > > > commit > > > > > history which lead up to the commit. This provides the > provenance > > > that > > > > > the > > > > > ASF needs for releases. Otherwise projects can mold their > > repository > > > > ref > > > > > structure any way they see fit. When a release vote is > successful > > > part > > > > > of > > > > > the release process should include tagging the voted upon comm= it > > SHA > > > > > under > > > > > rel/ to make it indelible. ('# git tag rel/v15.4.2 ' or > something > > > > > similar.) > > > > > > > > > > Let's incorporate the second point into our release process > > > immediately. > > > > We > > > > > can also go back and add corresponding tags in refs/tags/rel/ for > all > > > of > > > > > our past releases. Unless there are any objections I will take ca= re > > of > > > > this > > > > > housekeeping later this week. > > > > > > > > > > -- > > > > > Best regards, > > > > > > > > > > - Andy > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - Pi= et > > > Hein > > > > > (via Tom White) > > > > > > > > > > > > > > > > > > > > > -- > > > > Sean > > > > > > > > > > > > > > > > > > > -- > Sean > --089e01493c3200111a05293a0726--