Release New Fun: Difference between revisions
Jump to navigation
Jump to search
(First start for release documentation.) |
(Make approval workflow goals slightly more realistic given the overal goal of this release. Further tweaking likely.) |
||
Line 7: | Line 7: | ||
* To implement the minimum set of functionality required to deploy to production: | * To implement the minimum set of functionality required to deploy to production: | ||
** Display capabilities no more limited than what we have now. | ** Display capabilities no more limited than what we have now. | ||
** Modification capabilities similar to what we have now, but with | ** Modification capabilities similar to what we have now, but with as much as possible subject to an approval workflow. | ||
** Full edit access restricted by user permissions for anything that is not yet under an approval workflow. | |||
* To support the existing data and schema, with only the following minimal modifications: | * To support the existing data and schema, with only the following minimal modifications: | ||
** Drop unused columns. | ** Drop unused columns. |
Revision as of 07:17, 20 October 2008
GCD Web Site Release: New Fun
This is the main page for the first release of the new GCD Web Site, code-named New Fun. This page will holds general release-specific information plus links to documents on specific aspects of the release.
Release Goals
- To implement the minimum set of functionality required to deploy to production:
- Display capabilities no more limited than what we have now.
- Modification capabilities similar to what we have now, but with as much as possible subject to an approval workflow.
- Full edit access restricted by user permissions for anything that is not yet under an approval workflow.
- To support the existing data and schema, with only the following minimal modifications:
- Drop unused columns.
- Migrate user management to Django's authorization framework.
- To lay the groundwork for a new look-and-feel (including navigation and search capabilities) of the site which will support our growth into the new schema.
- To ship with a test suite that will support rapid but reliable future growth.
Detailed Requirements
Django Middleware
The following Django Middleware functionality needs to be integrated:
- Authentication
- Sessions
Feature Specifications
Detailed feature specifications will be recorded in Bugzilla under the New Fun milestone so that they may be assigned to developers and tracked.
Test Plans
- Test Data
- View-Level Tests
- Layout and Navigation Tests