From 140a0f85b83c568f3527367778cdab4ce5799ab9 Mon Sep 17 00:00:00 2001 From: echelon Date: Sun, 12 Feb 2012 16:40:27 +0000 Subject: [PATCH] spelling checks --- www.i2p2/pages/bounty_unittests.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/www.i2p2/pages/bounty_unittests.html b/www.i2p2/pages/bounty_unittests.html index cb848475..c0334cb6 100644 --- a/www.i2p2/pages/bounty_unittests.html +++ b/www.i2p2/pages/bounty_unittests.html @@ -3,7 +3,7 @@ {% block content %}

To improve I2P's maintainability, we want to have a solid set of automated unit tests for the critical code. While we do have some unit tests at the moment, they are ad-hoc and partly unfinished. -This bounty is for someone to check the existant tests and move over +This bounty is for someone to check the existing tests and move over old ones to jUnit, automate their execution, extend them to provide better code coverage, and publish the report online. Its a massive effort, but can be broken down into phases, listed below (phase 2 @@ -14,7 +14,7 @@ for college students, interns or anyone who is just interested.

Phase 1: CI jenkins and IRC bot

-Bounty: €in work by MathisDM
+Bounty: € in work by MathiasDM

To collect this bounty, a continuous integration server (Jenkins, old name was Hudson) must be set up and a connected IRC bot needs @@ -63,7 +63,7 @@ measured code coverage of 90% of the streaming lib

Phase 7: MultiRouter simulation

Bounty: €
-

To collect this bounty, the existant in-memory multi-router +

To collect this bounty, the existing in-memory multi-router simulation must be checked, made work again and extend to simulate lots of routers in memory on a single machine.