-0.9.0pre3:
-* connections fail if transport-plugin/nat produces
- some addresses that don't work (enable 'use_localaddr' with bindto for example,
- so that some of the 'local' IPs do not work due to the bindto); the result
- seems to be that the plugin tries some of the broken addresses, fails and the
- transport-level connection never comes up.
-* clean buildbots
-
-0.9.0pre4:
-* NAT library: [CG/MW]
- - UPnP support
- - testcase
- - more testing
-* Transport:
- - UDP fragmentation [MW]
- - decide how to deal with 'DISABLEV6' option (where does it live?)
- - integration of new NAT/plugin API with HTTP/HTTPS plugin
- - testing (again)
+0.9.0:
* GNUNET-GTK: [CG]
- - figure out where in the GUI we should show active upload operations and allow aborts
- - handle events:
- + search error
- + publish error
+ - provide context menus to allow aborts of downloads/uploads
+ - provide way to handle errors (search, download, publish errors)
+* new webpage:
+ - write chapter on DHT/block [Nate]
+ - make a NICE download page
+* big code review
+* Determine RC bugs and fix those (release should have no known real bugs)
+* Transport:
+ - When receiving SESSION_CONNECT: actually consider switching session
+ (test this!)
* FS [CG]
- implement multi-peer FS performance tests + gauger them!
+ insert
+ download
+ search
-
-0.9.0:
-* new webpage:
- - write chapter on DHT/block [Nate]
- - make a NICE download page
-* big code review
-* Determine RC bugs and fix those (release should have no known real bugs)
+* blocks:
+ + should block plugins live in block/ or with fs/dht/vpn?
0.9.1:
* TRANSPORT: [MW]
queue of size > 2), might be better to have at MOST one message pending
per plugin/target and only send the next one after the continuation was
called (or use 'notify_transmit_ready-style API?)
- - WLAN transport backend [DB]
+ - WLAN transport backend (code cleanup) [MW]
- need to periodically probe latency/transport cost changes & possibly switch transport
(working ATS)
-* DATASTORE: [CG]
- - check indexes / SQL for performance
* DV:
- proper bandwidth allocation
- performance tests
we have not 'used' (for their public keys) in a while; need a way
to track actual 'use')
- make sue we also trigger notifications whenever HELLOs expire
-* NAT:
- - repeatedly resolve hostname and look up interfaces to determine our own IP
* WLAN:
- nice signal strength adjustment [MW]
- energy cost in ATS [MW]