[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Stable releases - old versions
- To: or-talk@xxxxxxxx
- Subject: Stable releases - old versions
- From: grarpamp <grarpamp@xxxxxxxxx>
- Date: Thu, 30 Jul 2009 23:51:39 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 30 Jul 2009 23:51:43 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=vVq+RjCcPFzW5oAREqx3OcYhP8y4psG/WO0AkzVRdXw=; b=ETAd+2awuWf1EUnq4Ny6ZwwViyAmh8mpYjNO7g/6PQYK7kdJD5sFomN0pEdKPpo1iP qXu6YteRq0Hmr+YELTsPJz9we7Qcv56SjsGZdzsKYbnoXIx6mJBOJGoEnxM+eqmxI2AK nNPZIQwj3hAwhTehr9KrocUQsLdBPjJOT2rcU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=RyEunXJbVUmvSvsPAUBEtXxnHJV0K9Q4gw8aMQ/j+sV1cMj2aQdlBaok/SmAA76jeR rAuh80WLAFnK2dW2Dh8i3HMb0eYscBkWZ1C6vVQUdcwqeaeODesNfAuIScPF0SlBGGX1 OjF/Z7re6zaBEEvxl1pe1+HG7f0DmBD5uftJI=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Related to the blox* thread.
When 0.2.0.3x was marked stable, I went through and
mailed all the contacts running old versions. Some
profusly thanked, some silently updated, some ignored.
It would be handy if...
Upon marking and releasing a new stable branch, include
in the release notes what the minimum recommended versions
are and why [security breach, crashing, performance, needing
to break backward compat going forward, etc]... only
the really major reasons, just a few quotable lines. Some people
were like, why bother?
Make the contact field more of an encouraged option to use.
Maybe only a third of nodes had valid addresses.
Make Tor emit a logline hourly or at least daily when it notices
that it is old. Much more likely to stick out like that. Perhaps
graduate the verbosity/capitalization if it detects itself is not
in the current stable branch or older.
The torrc sample conf, man page, etc should mention the existance
of or-talk at the top of the relay configuration sections as something
operators should consider joining.
Consider an or-operator list should operator specific volume here
ever get high.
As an aside, I never bothered to inquire of anyone why their node
was so old. Those that offered it were:
- get around to it
- binary package/source deps/issues with their platform, user error
- bizarre security/performance rationalizations