From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C5F4215800C for ; Sat, 4 Mar 2023 05:39:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 223D8E0900; Sat, 4 Mar 2023 05:39:24 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0F77AE0900 for ; Sat, 4 Mar 2023 05:39:24 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 563B7340FB6 for ; Sat, 4 Mar 2023 05:39:23 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id EB2E773E for ; Sat, 4 Mar 2023 05:39:21 +0000 (UTC) From: "Sam James" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Sam James" Message-ID: <1677908348.c7b4f553a3e19a4ee3043a737fa8f0e55c516bbd.sam@gentoo> Subject: [gentoo-commits] proj/portage:master commit in: / X-VCS-Repository: proj/portage X-VCS-Files: DEVELOPING X-VCS-Directories: / X-VCS-Committer: sam X-VCS-Committer-Name: Sam James X-VCS-Revision: c7b4f553a3e19a4ee3043a737fa8f0e55c516bbd X-VCS-Branch: master Date: Sat, 4 Mar 2023 05:39:21 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 583b7bad-4457-47bf-8293-6f1dd3af0871 X-Archives-Hash: 50bd96aa969aa107f360d8b835b64cb5 commit: c7b4f553a3e19a4ee3043a737fa8f0e55c516bbd Author: Sam James gentoo org> AuthorDate: Sat Mar 4 05:39:08 2023 +0000 Commit: Sam James gentoo org> CommitDate: Sat Mar 4 05:39:08 2023 +0000 URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=c7b4f553 DEVELOPING: update release process Signed-off-by: Sam James gentoo.org> DEVELOPING | 42 ++++++++++++++++++++++++++++-------------- 1 file changed, 28 insertions(+), 14 deletions(-) diff --git a/DEVELOPING b/DEVELOPING index 3a97f1aa0..2f05d49b5 100644 --- a/DEVELOPING +++ b/DEVELOPING @@ -209,33 +209,47 @@ For a more detailed explanation (and rationalisation) of these rules: Releases -------- -Before starting: CI MUST BE GREEN! +0. Before starting: CI MUST BE GREEN! -First update: -- NEWS (for both new version & release date) -- setup.py +1. Repository mangling: + - Update NEWS (for both new version & release date) + - Update setup.py and commit. -Second create a git tag for this release: - git tag portage-3.0.30 +2. Create a git tag for this release: + git tag -a -s portage-3.0.30 -Create the tarball and run the tests: ./runtests -(see PYTHON_SUPPORTED_VERSIONS in runtests). +3. Create the tarball and run the tests: ./runtests + (see PYTHON_SUPPORTED_VERSIONS in runtests). -Version bump the ebuild locally (don't push) and verify it can re-install itself: - emerge --oneshot portage - emerge --oneshot portage # this is using the new Portage +4. Version bump the ebuild locally (don't push) and verify it can re-install itself: + emerge --oneshot sys-apps/portage + emerge --oneshot sys-apps/portage # this is using the new Portage -Publish the results (no going back now): +5. Publish the results (no going back now): - Push the new git tag - Upload the tarball - Commit the new ebuild version and tag the tracker bug for the commit -Create the release for pypi and upload it there: +6. Create the release for pypi and upload it there: - python -m venv .venv - . .venv/bin/activate - pip install wheel twine - python setup.py bdist_wheel sdist - twine upload dist/ -Close the bugs blocking the tracker bug for this release. +7. Bugzilla wrangling: + - Close the bugs blocked by the tracker bug for this release and + the tracker itself. + + - File a new bug in Portage Development > Core named + "[TRACKER] sys-apps/portage-${NEW_VERSION}" + with the 'Tracker' Bugzilla Keyword and the following text: + """ + Tracks bugs fixed in this release. + + 'Depends on' now means 'we want to fix this before release' + 'Blocks' means 'fixed in this release' + """ + +8. Done! Congratulations!