Release Onionoo 6.2-1.16.1

We'll have to put out a patch release for #27039 (moved). Let's do that today or tomorrow.

I'm preparing a release branch and pre-release tarball now.

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

Please review Onionoo commit 7d73a0c in my task-27113 branch, and please check the pre-release tarball.

How about we schedule deployment for 12:30 UTC today?

Trac:
Status: assigned to needs_review

Do we need to make some notes about how to upgrade via the intermediate JAR? Should that also have a release?

Also 12:30 UTC is fine.

The pre-release tarball looks good, assuming that we will be the only users of this release that are upgrading from the previous release. I feel we should at least have a pointer in the changelog to [comment:17] for anyone upgrading from 6.2-1.16.0. I've updated this comment to make it easier for others to follow.

and/or deciding if we want to add some release notes, maybe this is merge_ready we just haven't decided that yet.

Trac:
Status: needs_review to needs_revision

So, hmm, I think it's safe to assume that we're the only users of this release. But just in case somebody else runs their own Onionoo server and has never contacted us yet, what's the worst thing that can happen? It will take about a week for their responses to all follow the specification again. The only reason why we're using the tool from #27039 (moved) is to speed up this process. So, not using the tool is only about as bad as deploying the new release one week later. I'd think it's sufficient to mention your instructions on #27039 (moved) in the release announcement on the mailing list.

But if you feel strongly about this, we can also rewrite the change log and prepare another pre-release tarball. It'll take 10 minutes more. Up to you!

I will add the notes to the release mail as discussed in #tor-project.

Trac:
Status: needs_revision to merge_ready

This is now announced at https://lists.torproject.org/pipermail/tor-dev/2018-August/013390.html

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

closed