Fixed the invite process handling during joining to use

[silc.git] / TODO

diff --git a/TODO b/TODO
index 2e5e405946170c4ddb51c2e87930b2987e706160..830bd7361c977d52ecda8680457156ee26bcca2a 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,34 +1,19 @@
-TODO for Irssi SILC Client 1.0
-==============================
+TODO for SILC Client 1.0 branch
+===============================
 
- o bugs parsing nicknames with @ in NICK_CHANGE.
+ o Bugs reported on the mailing list that will be fixed eventually.
+   The numbers are arbitrary and assigned by me (c0ffee), bugs in
+   parentheses are fixed.
 
- o UTF-8 decode WHOIS userinfos, topic, etc.
-
- o Manaul file for silc(1) and silc.conf.
-
- o c0ffee's MIME signal
-
- o SILC protocol version 1.2 integration
-
- o Testing - See test plan:
-     http://silcnet.org/docs/silc-client-1.0-test.pdf
-     http://silcnet.org/docs/silc-client-1.0-test.ps
+   #1    Ignore ALL doesn't ignore target using /me
+   #2    specification of the silc network
+   (#3    expired private key dialogue doesn't work)
 
 
 TODO for SILC Server 1.0
 ========================
 
- o WHOIS search by public key in attrs.
-
- o Backup router related issues:
-
-       o Add special handling in router and server for "connection
-         timed out" error.  Be optimistic.
-
- o Manual file for silcd(8) and silcd.conf.
-
- o SILC protocol version 1.2 integration
+ o Check that founder key is distributed ok during backup resuming.
 
  o Testing
 
@@ -36,32 +21,22 @@ TODO for SILC Server 1.0
 TODO/bugs In SILC Libraries
 ===========================
 
- o Private key encryption to silc_pkcs_[save/load]_private_key[_data]
-   function.
+ o Test cases for all payload encoding and decoding routins in lib/silccore/
 
- o WIN32 silc_net_create_connection_async does not work the same way
-   than on Unix.  Do it with threads on WIN32.  The function works but
-   is not actually async currently (Fix this to 0.9.x).
+ o Test cases for math library routines in lib/silcmath/
 
 
 TODO in Toolkit Documentation
 =============================
 
-Stuff that needs to be done in order to complete the Tooolkit Reference
+Stuff that needs to be done in order to complete the Toolkit Reference
 Manual (Do these to 0.9.x).
 
- o Document the "notify" and "command_reply" client operations variable 
-   argument lists for all possible notify types and command replys.
-
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how
    new (external) projects can be glued into Toolkit (use irssi as an
    example), and how external projects can use Toolkit without gluing into
    it (how to link etc), debugging, architecture, types, etc.
 
- o Write "Platform Implementations" document to describe what platforms
-   Toolkit support, what has been implemented, what has not been, what
-   works differently etc.
-
- o Searching of predefined keywords, exact and partial matches (would be 
+ o Searching of predefined keywords, exact and partial matches (would be
    nice).