From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QRnu7-0002S7-QT for garchives@archives.gentoo.org; Wed, 01 Jun 2011 16:04:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C1AAB1C21F for ; Wed, 1 Jun 2011 16:04:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1452E1C147 for ; Wed, 1 Jun 2011 15:08:32 +0000 (UTC) Received: from [192.168.0.108] (ip-95-221-65-112.bb.netbynet.ru [95.221.65.112]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pva) by smtp.gentoo.org (Postfix) with ESMTPSA id EC3381B4008 for ; Wed, 1 Jun 2011 15:08:30 +0000 (UTC) Subject: RFC: better policy for ChageLogs (was: Re: [gentoo-dev] Council May Summary: Changes to ChangeLog handling) From: Peter Volkov To: gentoo-dev@lists.gentoo.org In-Reply-To: <20110530215552.GA3908@hrair> References: <4DD24EBE.5060002@gentoo.org> <1305886782.17955.29.camel@localhost> <1306757022.9216.36.camel@tablet> <20110530215552.GA3908@hrair> Content-Type: multipart/mixed; boundary="=-KiWi7DAnxGE4Uzz82WqE" Date: Wed, 01 Jun 2011 19:08:23 +0400 Message-ID: <1306940903.4416.20.camel@tablet> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Archives-Salt: X-Archives-Hash: cbf82e827fde12cb4f43bbca44873a97 --=-KiWi7DAnxGE4Uzz82WqE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =D0=92 =D0=9F=D0=BD=D0=B4, 30/05/2011 =D0=B2 14:55 -0700, Brian Harring =D0= =BF=D0=B8=D1=88=D0=B5=D1=82: > The problem is, that's a *fuzzy* definition.=20 Ok, let's start with something and then we'll add more items if required. Currently I'd like to propose following text: The ChangeLog must be updated with each commit. The only possible relaxations for this rule are: 1. Nonfunctional whitespace changes 2. Changes in comments (lines starting with # in ebuild, or leading text in patches) 3. Manifest updates 4. Changes in ChageLog itself ;) Something unclear? Anything else? -- Peter. --=-KiWi7DAnxGE4Uzz82WqE Content-Disposition: attachment; filename="text.xml.patch" Content-Type: text/x-patch; name="text.xml.patch"; charset="UTF-8" Content-Transfer-Encoding: 7bit diff --git a/ebuild-writing/misc-files/changelog/text.xml b/ebuild-writing/misc-files/changelog/text.xml index d92bbf4..eea927e 100644 --- a/ebuild-writing/misc-files/changelog/text.xml +++ b/ebuild-writing/misc-files/changelog/text.xml @@ -5,10 +5,21 @@

-The ChangeLog must be updated with each commit. The -echangelog tool should be used to create ChangeLog entries; -the format of a ChangeLog is now defined as "whatever -echangelog creates". +The ChangeLog must be updated with each commit. The only possible +relaxations for this rule are: +

+ +
    +
  • 1. Nonfunctional whitespace changes
    • +
  • 2. Changes in comments (lines starting with # in ebuild, or leading text in patches)
    • +
  • 3. Manifest updates
    • +
  • 4. Changes in ChageLog itself ;)
    • +
+ +

+The echangelog tool should be used to create ChangeLog entries; the +format of a ChangeLog is now defined as "whatever echangelog +creates".

--=-KiWi7DAnxGE4Uzz82WqE--