-0.9.0pre2:
-* BIG CORE REFACTORING:
- - fix transport plugin API (ATS!) [mw]
- - fix DV [nate]
-* Integration test:
- - test bootstrapping via hostlist + transport/core/dht connect
-* CORE:
- - Jun 27 11:51:54 core-7670 ERROR Assertion failed at gnunet-service-core.c:3616.
- (transport notified us that we connected to ourselves!!!; can we still reproduce this?)
- => Also, we may want to issue a 'connect to ourselves' automatically on start of
- core_api AND allow messages to self [CG/phillip]
-
-0.9.0pre3:
-* TRANSPORT: [MW]
- - [#1585, #1583, #1582] transport-level disconnect (i.e. TCP) does not cause core-level
- disconnect in a timely fashion (waits for connection timeout);
- need to figure a way to make it near-instant in those cases
- (i.e. rapid reduction in timeout on transport-level disconnect) [CG]
- => may have been fixed with instant-notification of disconnect
- to core on session-oriented connection hick-up; not perfect but
- likely good enough until we get ATS going; still should be tested...
- => "peers connected (transport)" now instantly goes to ZERO (core statistic),
- but "established sessions" stays up...
-* NAT/UPNP: [Milan / Ayush / MW]
- - [#1609] code clean up
- - testing
- - integration with transport service:
- + test TCP
- + implement UDP, HTTP/HTTPS
-* DHT: [Nate]
- - track paths content travels (PUT, reply-to-get) in messages,
- pass to client (client API & protocol already support this!)
-* FS: [CG]
- - implement multi-peer FS performance tests
+0.9.0pre4:
+* GNUNET-GTK: [CG]
+ - provide context menus to allow aborts of downloads/uploads
+ - provide way to handle errors (search, download, publish errors)
+* FS [CG]
+ - implement multi-peer FS performance tests + gauger them!
+ insert
+ download
+ search
-* GNUNET-GTK: [CG]
- - figure out where in the GUI we should show active upload operations and allow aborts
- - handle events:
- + search error
- + publish error
-* Determine RC bugs and fix those (release should have no known real bugs)
+* transport:
+ - CONNECT: actually consider switching session...
0.9.0:
* new webpage:
- - update books (especially for developers)
- - make a NICE download page and figure out how to enable developers to publish TGZs nicely
- - port "contact" page
-* FS migration:
- - exclude content that will "soon" expire from migration
- - make migration data rate & datastore IO-rate configurable
- - exclude certain peers as targets (based on hash values) in each
- iteration => same peer can only be picked every n-th iteration
- for the same content => fewer duplicate sending!
+ - 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)
+* Determine RC bugs and fix those (release should have no known real bugs)
0.9.1:
* TRANSPORT: [MW]
- - WiFi transport backend [DB]
- - Implement method of learning our external addresses from
- other peers; need some kind of threshold-based
- scheme, limiting both the total number of addresses that we accept
- this way as well as requiring multiple confirmations; also, we
- should possibly try to confirm that the given address works for
- us ourselves (loopback-style) before adding it to the list
- + we may be able to simplify WELCOME messages (no need to add
- addresses there anymore, but may help to learn them there anyway...).
- + we probably want some kind of voting/counting for learning IP addresses
- (maybe including IP addresses in ads proportional to how often others
- report them? we at least need some protection against >64k HELLOs!),
- + provide a way to give the user a list of "learned" IP addresses and
- a way to easily "veto" addresses off the list!
- => If MiM attacker uses vetoed address, blacklist the specific IP for
- the presumed neighbour!
- - need to periodically probe latency/transport cost changes & possibly switch transport
-* DV: [Nate?]
+ - 'TransmitFunction' requires plugins to have "unbounded" queue (or at least
+ 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]
+ - need to periodically probe latency/transport cost changes & possibly switch transport
+ (working ATS)
+* DV:
- proper bandwidth allocation
- performance tests
* PEERINFO:
- Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
- use different queue prioritization for probe-downloads vs. normal downloads
- re-implement gnunet-auto-share
-* UTIL: [CG]
- - allow limiting UNIX socket access by UID/GID
+ - implement 'GNUNET_FS_file_information_create_from_directory', avoiding
+ code duplication with gnunet-gtk's similar code (!)
* GNUNET-GTK: [CG]
- add tool bar
- do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
- finish publish dialog details:
+ normalize keywords (edit subdialog)
- implement download by URI dialog; figure out where to display those downloads!
-* ARM: [CG/Safey]
+ - add combo box to select desired mime type for search
+* ARM: [CG]
- better tracking of which config changes actually need to cause process restarts by ARM.
- handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
- discover dependencies between services
-* MONKEY: [Safey]
- - better crash management (attach debugging support, capture and analyze
- debug output, detect random vs. deterministic crashes)
- - '-m EMAIL' option for alternative e-mail TO
- - '-f FILENAME' option to write report to file instead of e-mail (for testing!)
0.9.2:
* PEERINFO: [NN]
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
-* TCP:
- - repeatedly resolve hostname and look up interfaces to determine our own IP
- - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
-* TRANSPORT:
- - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
- - WiFi transport backend
- * nice signal strength adjustment [MW]
- * energy cost in ATS [MW]
+* WLAN:
+ - nice signal strength adjustment [MW]
+ - energy cost in ATS [MW]
* BLOCKS:
- testcase would be nice
- - generic block support for DHT
* STATISTICS:
- - test notification-based statistics API
- implement statistics GUI (=> start from gnunet-gtk by button!)
* PEERINFO: [NN]
- move peerinfo to new GUI (=> start from gnunet-gtk by button!)
- rate limiting
- improved batching
- resource limit integration with ATS
-* VPN [PT]
- - TCP entry/exit
- - internal services
- - integration with DHT routing
+* VPN
+ - "DNS" .gnunet [MW]
+* MESH:
- optimized routes (beyond DHT/DV)
- - "DNS" .gnunet