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 1RJ6sg-00009A-J3 for garchives@archives.gentoo.org; Wed, 26 Oct 2011 17:03:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7D54221C040; Wed, 26 Oct 2011 17:02:56 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 9D6AC21C216 for ; Wed, 26 Oct 2011 17:02:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 1E4941B4031 for ; Wed, 26 Oct 2011 17:02:24 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Score: -1.626 X-Spam-Level: X-Spam-Status: No, score=-1.626 required=5.5 tests=[AWL=0.274, BAYES_00=-1.9] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NsUws6SfnNys for ; Wed, 26 Oct 2011 17:02:17 +0000 (UTC) Received: from amun.cheops.ods.org (amun.cheops.ods.org [83.161.135.166]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id C52431B4025 for ; Wed, 26 Oct 2011 17:02:16 +0000 (UTC) Received: from nut.cheops.ods.org ([2001:888:1022:0:ca2a:14ff:fe35:7a00] helo=gentoo.org) by amun.cheops.ods.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1RJ6rl-0006UN-VP for gentoo-dev@gentoo.org; Wed, 26 Oct 2011 19:02:15 +0200 Date: Wed, 26 Oct 2011 19:02:12 +0200 From: Fabian Groffen To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] [Council] ChangeLog generation within Gentoo Message-ID: <20111026170212.GD843@gentoo.org> Mail-Followup-To: gentoo-dev@gentoo.org 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 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/TIhMU+9tW3Jkwla" Content-Disposition: inline User-Agent: Mutt/1.5.21 (Darwin 11.2.0, VIM - Vi IMproved 7.3) Organization: Gentoo Foundation, Inc. X-Content-Scanned: by amun.cheops.ods.org (Exim Exiscan) using SpamAssassin and ClamAV X-Archives-Salt: X-Archives-Hash: 84557749fe6eb2757c515e960e573a95 --/TIhMU+9tW3Jkwla Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable All, As decided by the Council in its last meeting at the beginning of this month, ChangeLogs will not be generated from VCS commit messages, because the Council wants to keep the ability to edit generated ChangeLog messages [1]. As a result, the Council took this up with the Portage team, to make repoman update the ChangeLog file upon `repoman commit'. Because some of the reasons put forward for autogenerating ChangeLogs was the actual speed of making a commit, repoman does not call echangelog, but instead uses its information about the current state of the VCS directory it already collected to do its QA checks to write a ChangeLog entry directly from Python (in which repoman is written). To facilitate those developers who have echangelog, or their own scripts that do the same, hardwired into their systems, repoman commit will by default *NOT* update the ChangeLog if it is already modified. This allows to run echangelog followed by repoman commit, without getting a double ChangeLog entry. However, this also allows to do all kinds of other actions to the ChangeLog file, without actually adding an entry for the current change being committed, as we've already seen in practice. The Council would like to remind developers that it is still a requirement that all actions are documented in the ChangeLog and that it is hence the responsibility of the committing developer to make sure this requirement is met. Repoman in the most recent Portage versions in the tree, has an --echangelog flag, that takes the argument `y', `n' or `force'. The default for this option can be set to yes or no, and is controlled by metadata/layout.conf. For the `gentoo' (gentoo-x86) repository, this is set to true, which results in the previously described behaviour. When the ChangeLog is modified, but a new entry should still be written by repoman, --echangelog=3Dforce will accomplish this. Obviously, passing --echangelog=3Dn makes repoman skip writing a ChangeLog entry at all. The Council hopes to have informed all developers sufficiently through this message. [1] http://www.gentoo.org/proj/en/council/meeting-logs/20111011-summary.txt --=20 Fabian Groffen Gentoo on a different level --/TIhMU+9tW3Jkwla Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (Darwin) iEYEARECAAYFAk6oPRQACgkQX3X2B8XHTokDIwCfeWtHYSuJ6m+aLz4uzBbPc1Ov FsEAn2Wjf3uZb3+C9V6hWspUiejWYDCM =yiCU -----END PGP SIGNATURE----- --/TIhMU+9tW3Jkwla--