Support/Fennec Project Plan: Difference between revisions

Support/Fennec Project Plan (view source)

Revision as of 14:50, 26 May 2009

78 bytes removed , 26 May 2009

→‎Tasks

Djst

1,623

edits

@@ Line 3: / Line 3: @@
 =Tasks=
-#Audit code and make optional any dependencies on SUMO specific hardware and install options - 2 days - dev.<br/><br/>I don't think we have many, if any, but we need to be sure.
+#Audit code and make optional any dependencies on SUMO specific hardware and install options - 2 days - dev.
-#Extract required database schema and data for an "empty install"  - 3 days - dev<br/><br/>This consists of beginning with the base tiki install db, and adding to it any SUMO specific tables.  There is also a set of actual data required for SUMO, including permissions, admin option setup, and admin modules where the code is in the database.  I had a rough go at this just after the Summit last year, took me about a day to do a bad job at it.
+#*I don't think we have many, if any, but we need to be sure.
-#Create generic set of templates, with product name as a variable - 1 week - frontend dev<br/><br/>This is so that when the software is installed, it doesn't say "Mozilla Support".   We can hack what we already have into this easily.  Also need to remove links to Live Chat.  Since the other groups we have talked to about this don't seem to want to use Live Chat to begin with, we should defer productization of that component (and make it an optional module when we do, with separate installer).
+#Extract required database schema and data for an "empty install"  - 3 days - dev
-#Build admin interface for template configuration - 1 week - frontend dev<br/><br/>Depends on: 3<br/><br/>Need to be able to select and configure templates from the admin panel.  Should be straightforward.
+#*This consists of beginning with the base tiki install db, and adding to it any SUMO specific tables.  There is also a set of actual data required for SUMO, including permissions, admin option setup, and admin modules where the code is in the database.  I had a rough go at this just after the Summit last year, took me about a day to do a bad job at it.
-#Write install script (should cover database creation, setup.sh, htaccess.sh, any other needed items) - dev - 1 week<br/><br/>Depends on:  2, 3, 4<br/><br/>The goal is for users to be able to untar and ./install.sh and be ready to go.  The installer would need to take care of database user creation, locations of database server(s) and memcache servers (if used).
+#Create generic set of templates, with product name as a variable - 1 week - frontend dev
+#*This is so that when the software is installed, it doesn't say "Mozilla Support".   We can hack what we already have into this easily.  Also need to remove links to Live Chat.  Since the other groups we have talked to about this don't seem to want to use Live Chat to begin with, we should defer productization of that component (and make it an optional module when we do, with separate installer).
+#Build admin interface for template configuration - 1 week - frontend dev
+#*Depends on: 3
+#*Need to be able to select and configure templates from the admin panel.  Should be straightforward.
+#Write install script (should cover database creation, setup.sh, htaccess.sh, any other needed items) - dev - 1 week
+#*Depends on:  2, 3, 4
+#*The goal is for users to be able to untar and ./install.sh and be ready to go.  The installer would need to take care of database user creation, locations of database server(s) and memcache servers (if used).
 #Add a changelog to SUMO svn, listing changes from release to release - 5 minutes, plus 5 minutes for every commit.
-#Define and test packaging process - 3 days - dev<br/><br/>Depends on: 5, 6<br/><br/>This is basically testing and documenting the method for creating a downloadable package, which would include checking out code, removing any inappropriate files (.svn etc), reverting to defaults where needed.
+#Define and test packaging process - 3 days - dev
-#Define process for upgrade from one version to another (after product 1.0, thinking time 2-3 days, dev)<br/><br/>For each packaged release, we'll need to create a tarball.  If there are database changes, we will also need to create a database upgrade/downgrade script.
+#*Depends on: 5, 6
-#Document install process (1 day - dev + QA)<br/><br/>Depends on: 7
+#*This is basically testing and documenting the method for creating a downloadable package, which would include checking out code, removing any inappropriate files (.svn etc), reverting to defaults where needed.
+#Define process for upgrade from one version to another (after product 1.0, thinking time 2-3 days, dev)
+#*For each packaged release, we'll need to create a tarball.  If there are database changes, we will also need to create a database upgrade/downgrade script.
+#Document install process (1 day - dev + QA)
+#*Depends on: 7
 #Document administrative tasks where they differ from base Tiki (3 days - SUMO team)
 #Create list of KB articles to use as starting point, and extract required database data (Fennec specific, 3-4 days, SUMO team)
@@ Line 17: / Line 28: @@
 Critical dependency path for development: 1, 2, 3, 4, 5, 6, 7, 9
 =Time=