Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 652B91817B for ; Wed, 8 Jul 2015 13:17:59 +0000 (UTC) Received: (qmail 82060 invoked by uid 500); 8 Jul 2015 13:17:55 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 81963 invoked by uid 500); 8 Jul 2015 13:17:55 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 81941 invoked by uid 99); 8 Jul 2015 13:17:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2015 13:17:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of busbey@cloudera.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2015 13:15:40 +0000 Received: by laar3 with SMTP id r3so225602444laa.0 for ; Wed, 08 Jul 2015 06:17:28 -0700 (PDT) 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=WN0pKGu2XFM5IzM+D8SqewpQAgBViJMjTy80lp0ghbQ=; b=Mghu0Xu+KrarPW6Vl6X2O3835/QAsm5Lm+CxwPH3b/gPwcDyiIy9WKhSp2KvbAKXFv MG6XNtE/lZ5jVbugf80G4rYjiAEwTiC7c6hyd4y39HUovHJgBqOOoljWYzTFM3zg4uz5 BV3hKDT/gDvtoD1iDXVXa+xWU0DAyCTvE1SQfhMbbJy4l8jCa24OUtzggKotIHkL6qMN J6OBX6THugtgm5j33Rq3lzkhSR8T5HaSq9cMcfNkT37eadPjBbV05lx0LtON2aJ4imkB R1Wdr2+Xn3vG5KGXP4EEfDxjI2basTYyCVZwI5pMAmd3paIeZ0GJcTPyU+4ZPFJU8TNM AR1g== X-Gm-Message-State: ALoCoQm1vhr5sM/drN28QPEf56rN1NfBwAErrhmiSKzAS08wqaMTFRlKOBIaqRmM67xhcdH/IUzL MIME-Version: 1.0 X-Received: by 10.152.204.43 with SMTP id kv11mr9454230lac.15.1436361448201; Wed, 08 Jul 2015 06:17:28 -0700 (PDT) Received: by 10.25.152.82 with HTTP; Wed, 8 Jul 2015 06:17:28 -0700 (PDT) Received: by 10.25.152.82 with HTTP; Wed, 8 Jul 2015 06:17:28 -0700 (PDT) In-Reply-To: References: <82326C79-647B-4A3F-9BB6-3F1F66F0F7C2@altiscale.com> <222473374.4741621.1428008421715.JavaMail.yahoo@mail.yahoo.com> <559CC9C7.3000702@oss.nttdata.co.jp> Date: Wed, 8 Jul 2015 08:17:28 -0500 Message-ID: Subject: Re: IMPORTANT: automatic changelog creation From: Sean Busbey To: yarn-dev@hadoop.apache.org Cc: Hadoop Common , hdfs-dev@hadoop.apache.org, "mapreduce-dev@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11344a30e3b76b051a5cf5c8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11344a30e3b76b051a5cf5c8 Content-Type: text/plain; charset=UTF-8 On Jul 8, 2015 2:13 AM, "Tsuyoshi Ozawa" wrote: > > +1, thanks Allen and Andrew for taking lots effort! > > > Is there any possibility that, we can restrict someone from editing the > > issue in jira once its marked as "closed" after release? > > Vinay's comment looks considerable for us to me. What do you think? > Mistakes happen, even during the release process. Presuming the set of folks who can edit closed tickets is already restricted to contributors, why not assume any edits are the community making things more accurate? -- Sean --001a11344a30e3b76b051a5cf5c8--