Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

forms/templates: automate conversion of website content

Wiki Markup
ITinfo: write up types of documents; putting articles into normal content tree \[not done\]

Wiki Markup
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\]

Wiki Markup
deployment: stopgap deployment so we can start to test web app w/content (get runtime system setup) \[not done\]

Wiki Markup
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: new IA integrationfind a solution to ITinfo

WF: make it still bettern/a

forms/templates: start converting to new look-and-feel; add more contentcontinue automated conversion

ITinfo: integrate w/new IAfind a solution to filtering/searching for ITinfo items both at preview time & runtime

runtime: more webappget runtime system setup

other: more serious deployment n/a

Build 5: May 17

Theme: MIT certs: 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 

Build 6: May 31

Theme: real web app & deployment

testing: a simple smoke test to see if "build" is broken; 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?

Build 7: June 14

...

Theme: ready to test

Build 8: June 28

Theme: ready for migration