Jacob Appelbaum commited on 2008-03-10 08:41:46
Zeige 1 geänderte Dateien mit 22 Einfügungen und 2 Löschungen.
| ... | ... |
@@ -316,6 +316,25 @@ into the Tor network without adding undesirable n^2 traffic properties |
| 316 | 316 |
at the directory authorities. |
| 317 | 317 |
</li> |
| 318 | 318 |
|
| 319 |
+<li> |
|
| 320 |
+It would be useful to have automated build processes for Windows and |
|
| 321 |
+probably other platforms. The purpose of having a continuous integration |
|
| 322 |
+build environment is to ensure that Windows isn't left behind for any of |
|
| 323 |
+the software projects used in the Tor project or its accompanying.<br /> |
|
| 324 |
+Buildbot may be a good choice for this as it appears to support all of |
|
| 325 |
+the platforms Tor does. See the |
|
| 326 |
+<a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for |
|
| 327 |
+buildbot</a>.<br /> |
|
| 328 |
+There may be better options and the person undertaking this task should |
|
| 329 |
+evaluate other options. Any person working on this automatic build |
|
| 330 |
+process should have experience or be willing to learn how to build all |
|
| 331 |
+of the respective Tor related code bases from scratch. Furthermore, the |
|
| 332 |
+person should have some experience building software in Windows |
|
| 333 |
+environments as this is the target audience we want to ensure we do not |
|
| 334 |
+leave behind. It would require close work with the Tor source code but |
|
| 335 |
+probably only in the form of building, not authoring. |
|
| 336 |
+</li> |
|
| 337 |
+ |
|
| 319 | 338 |
<li> |
| 320 | 339 |
Tor needs to be far more tested. This is a multi-part effort. To start |
| 321 | 340 |
with, our unit test coverage should rise substantially, especially in |
| ... | ... |
@@ -323,11 +342,12 @@ the areas outside the utility functions. This will require significant |
| 323 | 342 |
refactoring of some parts of Tor, in order to dissociate as much logic |
| 324 | 343 |
as possible from globals.<br /> |
| 325 | 344 |
Additionally, we need to automate our performance testing. We've got |
| 326 |
-buildbot to automate our regular integration and compile testing already, |
|
| 345 |
+buildbot (except on Windows — see above) to automate our regular |
|
| 346 |
+integration and compile testing already, |
|
| 327 | 347 |
but we need to get our network simulation tests (as built in torflow) |
| 328 | 348 |
updated for more recent versions of Tor, and designed to launch a test |
| 329 | 349 |
network either on a single machine, or across several, so we can test |
| 330 |
-changes in performance on machines in different roles automatically. |
|
| 350 |
+changes in performance on machines in different roles automatically.<br /> |
|
| 331 | 351 |
</li> |
| 332 | 352 |
|
| 333 | 353 |
<li> |
| 334 | 354 |