updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index c972651c0cd7f583863f0e167d85c26e12d3da8c..92212fa4f6aed90fdd69144a297979b01556c5f3 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,10 +1,6 @@
 TODO for Irssi SILC Client 1.0
 ==============================
 
- o Signed message payload handling on UI
-
- o Check make install with static/shared libs
-
  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
@@ -13,9 +9,15 @@ TODO for Irssi SILC Client 1.0
 TODO for SILC Server 1.0
 ========================
 
- o Fix CUMODE_CHANGE and CMODE_CHANGE for founder key things.
+ o Check that +of works correctly when same client is +of already on
+   some other server on same channel.
+
+ o Check that founder key is distributed ok during backup resuming.
+
+ o Check that getting MOTD from other servers works.
 
- o 1.2 backup router support
+ o invite (with @server!*@host) not working from normal server/backup
+   router?
 
  o Testing
 
@@ -23,8 +25,6 @@ TODO for SILC Server 1.0
 TODO/bugs In SILC Libraries
 ===========================
 
- o Test cases for all cryptographic primitive in lib/silccrypt/
-
  o Test cases for all payload encoding and decoding routins in lib/silccore/
 
  o Test cases for math library routines in lib/silcmath/
@@ -33,21 +33,14 @@ TODO/bugs In SILC Libraries
 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).