Build 2: Apr 5
Theme: stabilize POC, begin runtime web app design
WF: make simple case really work
form/templates: automate conversion/import of existing content via script for a meaningful subset of real content; figure out structure of web project WRT to src/gen files
ITinfo: preview; prototype Prod Info
runtime: first whack at webapp design
for future: begin authN w/certs; synch w/Alf re: link mgmt; understand deployment
Build 3: Apr 19
Theme: dig into runtime web app
WF: box it up -- figure out what we know, what we need, and make Alf do the rest
forms/templates: automate conversion of website content
ITinfo: write up types of documents; putting articles into normal content tree \[not done\] |
runtime: have business requirements sorted; \[done\] have plan for add-on projects (scope v1 vs future); have a first-pass runtime web app for simple cases \[not done\] |
deployment: stopgap deployment so we can start to test web app w/content (get runtime system setup) \[not done\] |
testing: a simple smoke test; process for integration, testing, roll-out. Staging is our integration point, yet it is also the "ready to deploy" point. How do we do this? \[ not done\] |
Build 4: May 3
Theme: find a solution to ITinfo
WF: n/a
forms/templates: continue automated conversion
ITinfo: find a solution to filtering/searching for ITinfo items both at preview time & runtime
runtime: get runtime system setup
other: n/a
Build 5: May 17
Theme: get the runtime app (web server) going on ISDA-IST1, upgrade to Alf 2.01
WF: check in small changes to pooled & parallet WFs
forms/templates: get existing stuff working in 2.01; refine migrated content to go to "general" template when feasible; develop new templates at the next level
ITinfo:
- get a representation of the topic hierarchy (with numbers and names) as a static tree (later make it dynamic)
- in migration, turn keyword string in to separate field values; watch out for character issues w/encodings*
- describe all types of documents besides Stock Answers & Prod Info; start putting articles into normal content tree
runtime: design & implement first-pass runtime web app on Tomcat
deployment: stopgap deployment so we can start to test web app w/content
infrastructure: migrate to Alf 2.01 (partial)
Build 6: May 31 June 7
Theme: more Alf 2.01 integration, real web app & deployment
Task List:
- Forms/Templates: refine migration scripts to port content to "general" template when feasible
- Forms/Templates: develop new two column template for current pages
Forms/Templates: investigate ( design?) a template between "blob" and "general" which has header+footer+left nav+right blob - investigation showed little utility for a midway template.- Content Migration: develop scripts to identify pages which are blue-box, redirects, news or otherwise questionable for migration
- Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.
- Content Migration: Update wget of IS&T site on bi-weekly basis and run scripts to capture changes from step above as well as new pages
- ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)** Step 1: put hierarchy into JSP in a form that ALfresco web forms can use as a drop-down list.** ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms
<unnecessary> -ITinfo: in migration, turn keyword string in to separate field values; watch out for character issues w/encodings- - Itinfo: Verify that Google search either uses the keyword string as-is or ignores keywords completely (in which case we may decide to discard keyword data)
- ITinfo: start putting articles into normal content tree
- ITinfo: document how to do content export
*\[Steve\] \[Joe\] \[Catherine\]* |
Runtime: layout high level architecture of webapp (Spring, MVC, security, sub-components, etc.) & assign areas- Runtime: Create svn module for runtime app as a Netbeans project** advise on use of Acegi in app
*\[DaveT\] \[Hunter\]* |
Runtime: develop Acegi implementations of Moira lists for access control (may involve a web service. Or not)**
- set up supporting db or other infrastructure*
- create impl ** will need to be refactored, as it is not going to be done in one build
- Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
- Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
- Hunter] Deployment: stopgap deploy-to-filesystem so we can start to test webapp w/content** design deployment approach for runtime** Set up apache, tomcat, smb on isda-ist1
- Testing: a simple smoke test to see if "build" is broken
- Testing: define a process for integration, testing, roll-out. Staging is our integration point, yet it is also the "ready to deploy" point. How do we do this?
- Infrastructure: Continue to integrate 2.0.1 on isda-cs1
- Fix/workaround bugs https://confab.mit.edu/jira/browse/WCM-87, https://confab.mit.edu/jira/browse/WCM-88, https://confab.mit.edu/jira/browse/WCM-93, and https://confab.mit.edu/jira/browse/WCM-94.
- New IA Migration: create JSP to consume RSS feed
Detailed Release Notes:
Build 7: June 21
Theme: real web app, real deployment, ready to test?
- ~ Forms/Templates: refine migration scripts to port content to "general" template when feasible- First round of general template migration completed
- Forms/Templates: develop new two column template for current pages
- Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.- work ongoing- new lists distributed June 20 for blue-box, redirects and non-conforming pages.
- Content Migration: Update wget of IS&T site on bi-weekly basis and run scripts to capture changes from step above as well as new pages- wget from June 9 analyzed and migrated.
- Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun.
Build 8: July 5
Theme: ready for migration