summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorpjmattal <pjmattal>2005-02-06 16:39:46 +0000
committerpjmattal <pjmattal>2005-02-06 16:39:46 +0000
commit890987fb9b7daf347d059d396b9e4f36c8651197 (patch)
tree276dce1aa7ecda2700e5049541918e3546c783e3
parent7ca7f7a584406f8ea4d93a0d10524e35b7a1dc07 (diff)
modified LAUNCH.txt
-rw-r--r--LAUNCH.txt7
1 files changed, 1 insertions, 6 deletions
diff --git a/LAUNCH.txt b/LAUNCH.txt
index 00eb91f..f04a51d 100644
--- a/LAUNCH.txt
+++ b/LAUNCH.txt
@@ -2,20 +2,15 @@ This is the list of things we need to get done by 2/15 in order to make a
3/1 launch happen. Feel free to add items to it as they come up, and put "DONE" next to things as you finish them.
TIER 1 (critical)
-* password crypt in php code - DONE
-* handle crypt passwords correctly in tupkgs - DONE
-* db code in tupkgupdate for package updates/additions - Paul - DONE
-* functionality to delete packages in unsupported (but not in AUR) - IN PROGRESS
* a package should be made of tupkg client tool
TIER 2 (pretty important)
* tupkg and tupkgs should not output unhashed passwords
* config file capability for tupkg client in user's homedir
* email notification of errors in tupkgupdate - Paul
-* move config options for php code to separate file and make that file
- a ".proto" file in svn - DONE
* add foreign key constraints with on delete cascade to make sure
entries are not orphaned in PackageSources and PackageDepends
+* migrate to InnoDB tables?
TIER 3 (noncritical)
* tupkgupdate should use updatesync instead of gensync - Paul