Release metrics-lib 2.6.0

Let's put out a new metrics-lib release for #30216 (moved). I'll prepare a branch and tarball shortly.

added component::metrics/library owner::karsten priority::medium resolution::fixed reviewer::irl severity::normal status::closed type::task labels

Branch: https://gitweb.torproject.org/user/karsten/metrics-lib.git/log/?h=task-30329

Tarball: https://people.torproject.org/~karsten/volatile/metrics-lib-2.6.0.tar.gz

Trac:
Reviewer: N/A to irl
Status: assigned to needs_review

[√] Release version is set [×] Changelog looks sane [√] Tarball created with "ant tar" is same size (not byte-for-byte due to timestamps) [√] Tests pass [√] Checks pass

We should mention in changelog that we are no longer signing jars.

Trac:
Status: needs_review to needs_revision

Ah, good point about the change log. Hang on, I'll prepare a new branch and tarball...

Same links, please take another look. Thanks!

Trac:
Status: needs_revision to needs_review

[√] Release version is set [√] Changelog looks sane [√] Tarball created with "ant tar" is same size (not byte-for-byte due to timestamps) [√] Tests pass [√] Checks pass

I have signed the git tag metrics-lib-2.6.0/irl in my repository https://github.com/irl/metrics-lib.git which can be merged into the metrics-lib repository. This tag was created with:

git tag -a -s -m "Tor Metrics' metrics-lib Release 2.6.0" metrics-lib-2.6.0/irl

You should then be able to make a tag metrics-lib-2.6.0/karsten with a GPG signature from you, and then one unsigned tag in the repo as usual. It's not possible to do multi-signature-tags in a standard way unfortunately.

Trac:
Status: needs_review to merge_ready

Release: https://dist.torproject.org/metrics-lib/2.6.0/

Closing. Thanks!

Trac:
Resolution: N/A to fixed
Status: merge_ready to closed

closed