aboutsummaryrefslogtreecommitdiff
path: root/ReleaseNotes
Commit message (Expand)AuthorAge
* put 0.2.1.24 in release notes tooRoger Dingledine2010-02-21
* give it a blurb, update the dateRoger Dingledine2010-02-13
* prepare for 0.2.1.23Roger Dingledine2010-02-12
* bump to 0.2.1.22, and give it a changelogRoger Dingledine2010-01-19
* bump to 0.2.1.21 so we can releaseRoger Dingledine2009-12-21
* add the 0.2.1.20 changelog blurb, plus update the releasenotesRoger Dingledine2009-11-17
* credit optimist for the bug 1038 diagnosisRoger Dingledine2009-07-28
* put in the full 0.2.1 release notesRoger Dingledine2009-07-24
* forward-port the 0.2.0.35 release notesRoger Dingledine2009-07-24
* If the bridge config line doesn't specify a port, assume 443.Roger Dingledine2009-04-11
* and forward-port the 0.2.0.33 and 0.2.0.34 changelogsRoger Dingledine2009-02-11
* and forward-port the 0.2.0.33 changelogRoger Dingledine2009-02-04
* put recent release blurbs into the changelog; fix a typo in tor-spec.Roger Dingledine2008-12-11
* and forward-port thoseRoger Dingledine2008-11-22
* forward-port the 0.2.0.31 changelogRoger Dingledine2008-09-08
* minor grammar fixRoger Dingledine2008-08-31
* minor fixesRoger Dingledine2008-08-04
* integrate the 0.2.0.29-rc items into the release notesRoger Dingledine2008-07-16
* fix up a confusion on the release notes (thanks karsten)Roger Dingledine2008-07-09
* first draft of the Tor 0.2.0.x Release Notes.Roger Dingledine2008-06-30
* flush some changes in my sandbox -- ancient changelog typos, etcRoger Dingledine2008-06-07
* and forward-port thoseRoger Dingledine2008-01-19
* forward-port the 0.1.2.18 entriesRoger Dingledine2007-11-11
* and synchronize that with the ReleaseNotes fileRoger Dingledine2007-10-22
* whoops, we've been failing to update the ReleaseNotes fileRoger Dingledine2007-09-28
* forward-port the 0.1.2.13 changelog and releasenotesRoger Dingledine2007-04-24
* add a new file ReleaseNotes that contains just theRoger Dingledine2007-01-25