From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 01AC53858D28 for ; Fri, 3 Nov 2023 18:33:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 01AC53858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 01AC53858D28 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1699036405; cv=none; b=DJ9RLnCdxL0sV+U+3ZCQRPNHG2MB/3afXyA68XXatTdjApEUfafO4JA5fWJ28jD8r91Y0jF+RBjWvHxbjpbT8706tgNLLNf0bLQzLkJ2z6x8sTYkvsPrcpiAIDmjKPO7z5hvC7Q5pD3QN6DLnKroCWCtnQDkO2P1o2v92hRkg2k= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1699036405; c=relaxed/simple; bh=YN1CLt+vq8LtTwEQMLIClCenKNXuN6zzHmBlCOmTT2E=; h=Message-ID:Subject:From:To:Date:MIME-Version; b=E6ajiALeeCmEt0e/oYAjOr9+rGs9KrHG2XLP/FDKGQfjosYsYWKhKS+CUDu+f/yNmgDXhmW6sVLhoBYnQ3P7vxRSNThk0z+hoLdovlZYYTH/AGscPnMN5/gCQ5zlnlBmhMZas8q6byLiyAkUP7A6plo1HUrBb8zwdIPHwzU+kdg= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from r6.localdomain (82-217-174-174.cable.dynamic.v4.ziggo.nl [82.217.174.174]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 17FD6302FDC3 for ; Fri, 3 Nov 2023 19:33:09 +0100 (CET) Received: by r6.localdomain (Postfix, from userid 1000) id D3600340430; Fri, 3 Nov 2023 19:33:08 +0100 (CET) Message-ID: <002cb7f24b6c4584880a8ae263778e5a4ee80378.camel@klomp.org> Subject: Creating an elfutils release From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Fri, 03 Nov 2023 19:33:08 +0100 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 X-Spam-Status: No, score=-3026.7 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Although most things are automated there are a couple of manual steps. I thought I would write those down, so others can also create a release. - Pre-release, go over any pending patches or recently updated bugs making sure there isn't anything urgent (or note those as known issues in the release notes). https://patchwork.sourceware.org/project/elfutils/list/ https://sourceware.org/bugzilla/buglist.cgi?bug_status=3DUNCONFIRMED&bug_st= atus=3DNEW&bug_status=3DASSIGNED&bug_status=3DSUSPENDED&bug_status=3DWAITIN= G&bug_status=3DREOPENED&&order=3DLast%20Changed&product=3Delfutils&query_fo= rmat=3Dadvanced - Make sure the buildbot CI is all green https://builder.sourceware.org/buildbot/#/builders?tags=3Delfutils Also check the build-only builders (currently only sparc) https://builder.sourceware.org/buildbot/#/builders?tags=3Delfutils-build And the snapshots (currently only coverage) https://builder.sourceware.org/buildbot/#/builders?tags=3Delfutils-snapshot= s The actual latest coverage results can be found at: https://snapshots.sourceware.org/elfutils/coverage/latest/ You can compare with the coverage of the last release: https://sourceware.org/elfutils/coverage/ - Create the last "prepare" commit. - Edit NEWS to include any noteworthy new items come up with a "release name" - Update version in configure.ac Check/update AC_COPYRIGHT year. Check/update lib/printversion.c year. - Update po files and config/elfutils.spec.in by running: autoreconf -f -v -i && \ ./configure --enable-maintainer-mode && \ make distcheck -j12 after making the above updates. (This will also check that a dist can be created and a build and check can be done from that). - Double check the config/elfutils.spec.in changelog entry (often needs to be hand edited to adjust whitespace) - commit the NEWS, configure.ac, regenerated po and config/elfutils.spec.in - push - Good to wait for buildbots to do one last check. - tag and sign the last commit: git tag --sign elfutils-0.1xx -m "elfutils 0.1xx release" - git push --tags (Note that this might also push annotated tags you might have imported from other remotes, so check with git push --tags -n first) - Create and upload the release. Requires having sourceware scp access. - config/upload-release.sh 0.1xx This will do a new checkout using the given tag, verifies the tag signature, does a make dist, signs the dist tar ball and uploads dist and sig files. - Update the latest coverage in the website. checkout elfutils-htdocs.git ./update-coverage.sh 0.1xx This does a fresh checkout and runs make coverage Generating a new diff to commit. Check with git show then git push. - Sent out a "elfutils 0.1xx released" announcement to elfutils-devel@sourceware.org (preferably pgp signed) include URLs to download the NEWS section git shortlog elfutils-0.1xx-1.. | sed -e 's/ //' - Add release (notes) to website. Find release announcement permalink on https://inbox.sourceware.org/elfutils-devel/ in elfutils-htdocs add it under "release notes" in index.html git commit -a -m "Add 0.1xx release notes" && git push - Update the #elfutils irc.libera.chat channel topic revealing the new version and "code name".