Apart from the below, we still need:
- More complete translations. 1145 introduces a few new strings, but
apparently we have a complete translation thanks to ph00 and Singularity.
Lots of translations have been started and then stopped, and if you can do a
new language in time (i.e. by Wednesday), that'd be great.
- More seednodes. If you have a node with reasonable upstream bandwidth and
which is not NATed, please turn on the seednode option, and send us your
opennet noderef.
On Tuesday 29 April 2008 21:24, Matthew Toseland wrote:
> It is our intention to release 0.7.0-final late next week.
>
> We (myself and ian) would really appreciate any testing you can do. Please
> test, test, test, let us know of any serious issues, ideally report them in
> the bug tracker (https://bugs.freenetproject.org), or via FMS if you must
> remain anonymous. If they have already been reported, find the old bug and
> comment on it and I will see it.
>
> If you can do some usability testing, that's really valuable. All you do is
> find somebody who hasn't used Freenet before, and get them to install a
node.
> Don't give them any help unless they get *really* stuck. Report their
> complaints, and anywhere where they got stuck: these are bugs, but it's
> probably best to report them here.
>
> The last lot of usability testing I did threw up a couple of biggish bugs:
the
> user couldn't see the bookmarks because of all the useralerts, so didn't
know
> what to do with Freenet; and plugin downloads were taking ages during
> install. Both are fixed now.
>
> After 0.7.0, we will move towards 0.7.1. Thanks to Google, we have a
breathing
> space for 6 months, and we intend to use this to get more users by making
> Freenet faster, easier to use, and more secure. In roughly that order: most
> of the ease-of-use low-hanging-fruit has been dealt with for 0.7.0, which
> means performance is the main thing. Security is important but some of the
> big changes we need to do will take considerable time so should be postponed
> for 0.8.0.
>
