
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Karsten, 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? thanks, Nusenu [1] https://lists.torproject.org/pipermail/onionoo-announce/2015/thread.html -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVFeWsAAoJEFv7XvVCELh0aeYP/R9pkcPgMGttspr5cl1W1RM+ qeIutnhNDAMs+DcbHKmB19BzgSRUfzrm4DCqnizWIxdXcF+AQP2nhmP0y+hIWTrK 5ctBQsWMUiwHym0TcKbbIEHrP2BcIoQSIM1GG52G4OWfmoymjbi5J1Jd+KuXYsFr 8GtJlLkjHWcD8wQuCUtMSfq1tTK/XnQES/UfhTUfJ3TMZvR1wxD3BNWZFJSOFMP2 k7cfBLYSG2uRCyRZ8dkoLXnSeJ/aya2PqR41mvU5y+IdUHC8IoVItx3GhC4ZT2v1 YcQyxvVFZh0NEwrdnYIxErNN5CJjqDUyLPWVQPJGvKR1KgFVdtcqsJH8OsyvYW1y ysETJ9AXPReo9os+oAWVJZvFG1HwU6MzS4U7beuVMo3drzNh3433nkZbCX50hS4z WMUdsWjZgUNscAIj76ECI58wiTgYN8Ro5X9wY9LwSwJz7NHtc+a999xSLy3GUuUp vEerRa1k06PqeqpNsZoe/8WVwohZVtRc9oGTcXJgtRF3F3hltsqB6s03hGLsQfXJ roOFglxrUlBaGAVYlyLWHSDiPf2lVnNUF27nsGodjoTLEubsJ1BsxUqT1JTNi3yx k8WTU2ATfbTVKva0N7Ac3yBE8+ZkQ+YbZB839li9ocXuxi173/aNmG3mKOVWWhP2 x0C/WXllxI2ObZY05ryR =IfVc -----END PGP SIGNATURE-----

-----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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJVFlTwAAoJEJD5dJfVqbCrjQAH/1Hw3il3J2lJB4js4EgeLZi/ BevLLCgcrsDnylfYBvs7kyBh2affmtp98EfOEhDmJpjXMIDgHH2t1243/lqtHg1a HWFSIptwMZPWh5ExFAppoEefiN5hKL/V8O+ImlpiTsJuf8ZQTwpNNtnv434Pd98N FQDSnf5yOqZDPWwlSiI4ppLEmOsQUDkz7n1Rb3R8LTw2HmiQHy9hbPmOS7Tqc4b/ 64x6gh64+2YnVESWuWSpVYlyXhbYYnCfUmea3e0MRwShblO3U4rZWDQ1ACbvivAG Gu8FXLouDVUjg9yWeenVR/WS56d6jQeu13thvvLwaZCCnfyrlLzAdydUb7VTYOI= =wP/6 -----END PGP SIGNATURE-----
participants (2)
-
Karsten Loesing
-
Nusenu