-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 28/03/15 00:20, Nusenu wrote:

Hi Karsten,

Hi Nusenu,

the latest onionoo update 2.3 triggered a bug in my onionoo "client" (charset encoding). Even though it is a bug on my side, would you mind announcing future releases/deployments on onionoo-announce [1] including a short changelog?

Oh, I didn't expect the 2.3 update to break anything. The change to 2.3 was just that we added optional "flags" field to uptime documents on March 22, 2015.

The charset encoding things were bugfixes which still happened as part of 2.2.1 (which numbers being major protocol version, minor protocol version, and implementation version). I had no idea these fixes would break clients. Oops.

In theory, only a major protocol update would break clients. That's why there's the "next_major_version_scheduled" field that gives you hints about upcoming changes, and that's what onionoo-announce@ is for. I'm not sure if it's a good idea to announce implementation changes there, mostly because there are so many of them.

One thing I have been thinking about: should I move announcements to the tor-dev@ mailing list, rather than having the special-purpose mailing list onionoo-announce@? It's only been four messages in the past six monts, and maybe more people would notice. (I noticed when arguing against a special-purpose tor-bridges@ mailing list, because we already have tor-relays@.)

By the way, I should indeed start a changelog for implementation changes. There's already the protocol version log on the protocol page (https://onionoo.torproject.org/protocol.html#general), but I should also put a more detailed log into the source repository.

Thanks for the feedback!

All the best, Karsten