remove warning about old darcs v1, change allmydata.org to tahoe-lafs.org

[Imported from Trac: page Dev, version 100]
zooko 2011-05-31 17:04:47 +00:00
parent 81b764b9cc
commit 57c429ed1d

7
Dev.md

@ -34,11 +34,10 @@ Views into the process of Tahoe-LAFS hackery.
## Tools
* [tahoe-lafs-trac-stream](http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream) mailing list is the way to receive lots of emails from trac
* [ViewTickets](ViewTickets)
* Sources for Tahoe-LAFS and its side-projects are browsable via the "Browse Source" button at the top of each [project site](http://allmydata.org/trac)
* To fetch the source code using [darcs v2](http://darcs.net): `darcs get --lazy <http://allmydata.org/source/tahoe-lafs/trunk> tahoe-lafs`
* `darcs v2` is highly recommended over `darcs v1`. If you really don't want to install `darcs v2`, then you can use `darcs v1` instead, but you'll have to run a slightly different command-line and be prepared to wait for tens of minutes for the initial `get` to finish. The command-line for `darcs v1` is: `darcs get <http://allmydata.org/source/tahoe/trunk-darcs1format> tahoe`.
* Sources for Tahoe-LAFS and its side-projects are browsable via the "Browse Source" button at the top of each [project site](http://tahoe-lafs.org/trac)
* To fetch the source code using [darcs](http://darcs.net) (version 2.0 or newer): `darcs get --lazy <http://tahoe-lafs.org/source/tahoe-lafs/trunk> tahoe-lafs`
* there is an experimental git mirror of the darcs repository (not necessarily up-to-date) [on github](http://github.com/warner/tahoe-lafs).
* <http://allmydata.org/source/tahoe/tarballs/> contains snapshots of current source code.
* <http://tahoe-lafs.org/source/tahoe/tarballs/> contains snapshots of current source code.
* The Buildbot page (linked at the top of each page) shows current build and test results. See the [BuildbotPolicy](BuildbotPolicy) page and [HowtoContributeABuildbot](HowtoContributeABuildbot) page.
* The Timeline (linked at the top of each page) shows changes to the source code, the issue tickets, and the wiki (i.e. this web site).
* [/../../tahoe-figleaf/current The code coverage statistics] show which lines of code get exercised by the unit tests.