modified LAUNCH.txt

This commit is contained in:
pjmattal 2005-02-06 16:39:46 +00:00
parent 7ca7f7a584
commit 890987fb9b

View file

@ -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. 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) 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 * a package should be made of tupkg client tool
TIER 2 (pretty important) TIER 2 (pretty important)
* tupkg and tupkgs should not output unhashed passwords * tupkg and tupkgs should not output unhashed passwords
* config file capability for tupkg client in user's homedir * config file capability for tupkg client in user's homedir
* email notification of errors in tupkgupdate - Paul * 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 * add foreign key constraints with on delete cascade to make sure
entries are not orphaned in PackageSources and PackageDepends entries are not orphaned in PackageSources and PackageDepends
* migrate to InnoDB tables?
TIER 3 (noncritical) TIER 3 (noncritical)
* tupkgupdate should use updatesync instead of gensync - Paul * tupkgupdate should use updatesync instead of gensync - Paul