...
infrastructure: migrate to Alf 2.01 (partial)
Build 6: May 31 June 7
Theme: more Alf 2.01 integration, real web app & deployment
...
| Wiki Markup |
|---|
*\[Ann-Patrice\]* |
Forms/Templates: refine migration scripts to port content to "general" template when feasible| Wiki Markup |
|---|
*\[Ann-Patrice\]* |
Forms/Templates: develop new two column template for current pages
| Wiki Markup |
|---|
*\[Ann-Patrice\]* |
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.-
| Wiki Markup |
|---|
*\[Ann-Patrice\]* |
Content Migration: develop scripts to identify pages which are blue-box, redirects, news or otherwise questionable for migration -
| Wiki Markup |
|---|
*\[Ann-Patrice\]* |
Content Migration: work with Publications side to eliminate pages which are not going to move on to new design. | Wiki Markup |
|---|
*\[Ann-Patrice\]* |
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
| Wiki Markup |
|---|
*\[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**
| Wiki Markup |
|---|
*\[Craig\] \[DaveT\]* |
advise on use of Acegi in app | Wiki Markup |
|---|
*\[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?
-
| Wiki Markup |
|---|
* \[Joe\]* |
Infrastructure: Continue to integrate 2.0.1 on isda-cs1 -
| Wiki Markup |
|---|
* \[Joe\]* |
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?
Build 8:
...
July 5
Theme: ready for migration