...
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:
[Ann-Patrice] Forms/Templates: refine migration scripts to port content to "general" template when feasible, first pass- [Ann-Patrice] Forms/Templates: develop new two column template for current pages
- [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.
- [Ann-Patrice] Content Migration: develop scripts to identify pages which are blue-box, redirects, news or otherwise questionable for migration
- [Ann-Patrice] Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.
- [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
- [Steve] ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)
- [Steve] Step 1: put hierarchy into JSP in a form that ALfresco web forms can use as a drop-down list.
- [Steve] ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms
<unnecessary> [Steve] -ITinfo: in migration, turn keyword string in to separate field values; watch out for character issues w/encodings- - [Steve] 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)
- [Steve] ITinfo: start putting articles into normal content tree
- [Steve] 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
- [Joe] Runtime: Create svn module for runtime app as a Netbeans project
- [Craig] [DaveT] 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) WE CAN USE LDAP** [Hunter] set up supporting db or other infrastructure
- [DaveT] create impl ** will need to be refactored, as it is not going to be done in one build
- [Steve] Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
- [Joe] Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
- [Joe, Hunter] Deployment: deploy-to-filesystem
- [Joe] design deployment approach for runtime
- [Hunter] Set up apache, tomcat, smb on isda-ist1
- [Who?] Testing: a simple smoke test to see if "build" is broken
- [Who?] 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?
- [Joe] Infrastructure: Continue to integrate 2.0.1 on isda-cs1
- [Joe] Fix/workaround bugs https://confab.mit.edu/jira/browse/WCM-87
...
- ,
...
...
- ,
...
...
- ,
...
- and
...
- https://confab.mit.edu/jira/browse/WCM-94.
- [Steve] 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?
- [Ann-Patrice] Forms/Templates: refine migration scripts to port content to "general" template when feasible- First round of general template migration completed
- [Ann-Patrice] Forms/Templates: develop new two column template for current pages
- [Ann-Patrice] 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.
- [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- wget from June 9 analyzed and migrated.
- [Ann-Patrice] Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun.
| Wiki Markup |
|---|
]{color}{color:#000000}.{color} * !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif! {color:#006600}*\[Steve\]*{color} New IA Migration{color:#000000}: create JSP to consume RSS feed{color} *Detailed Release Notes:* h2. Build 7: June 21 Theme: real web app, real deployment, ready to test? * !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif! {color:#006600}*\[Ann-Patrice\]*{color} Forms/Templates: refine migration scripts to port content to "general" template when feasible\- First round of general template migration completed * {color:#006600}*\[Ann-Patrice\]*{color} -Forms/Templates:- _-develop new two column template for current pages-_ * !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif! {color:#006600}*\[Ann-Patrice\]*{color} 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. * !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif! {color:#006600}*\[Ann-Patrice\]*{color}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. * {color:#006600}*\[Ann-Patrice\]*{color} Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun. {dynamictasklist:Build 7 June 21} h2. Build }{dynamictasklist} |
Build 8:
...
July
...
5
...
Theme:
...
ready
...
for migration
- [Ann-Patrice
...
- ]
...
- Forms/Templates:
...
- refine
...
- migration
...
- scripts
...
- to
...
- port
...
- content
...
- to
...
- "general"
...
- template
...
- when
...
- feasible
...
- -
...
- second
...
- round
- [Ann-Patrice
...
- ]
...
- Forms/Templates: develop new two column template for current pages
- [Steve] 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.
- [Ann-Patrice] Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - next round (To be specified in more detail)
- [Steve] ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)
- [Steve] ITinfo: separate into a pure XML document and a JSP that reads this and formats it for Alfresco web forms
- [Steve] ITinfo: start putting "news" and "articles" into normal content tree
- [Ann-Patrice] make forms for "news" and "articles"
- [Steve] add automatic "guid" generation function to ITInto web forms
- [Steve] scripts to export data & format into xml, ready to load
- [Steve] load data into alfresco, to be managed via webform
- [Steve] 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)
- [Steve] Helpdesk questions:
- [Steve] what about Top 5? what is the requirement?
- [Steve] Help desk portal page - determine features, integration points
- [Steve] Find out how Help Desk Wiki will get articles into Alfresco
- [Joe] make .htaccess emulation work for ordinary content
- [Who?] Testing: a simple smoke test to see if "build" is broken
| Wiki Markup |
|---|
{dynamictasklist:AnnPatrice}{dynamictasklist} |
| Wiki Markup |
|---|
{dynamictasklist:Steve}{dynamictasklist} |
| Wiki Markup |
|---|
{dynamictasklist:Joe}{dynamictasklist} |
| Wiki Markup |
|---|
{dynamictasklist:Unassigned}{dynamictasklist _develop new two column template for current pages_ * {color:#006600}*\[Ann-Patrice\]*{color} 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. * {color:#006600}*\[Ann-Patrice\]*{color} Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - next round (To be specified in more detail) * {color:#006600}*\[Steve\]*{color} {color:#000000}ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic){color} ** {color:#006600}*\[Steve\]*{color} {color:#000000}ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms{color} * {color:#006600}*\[Steve\]*{color} {color:#000000}ITinfo:{color} start putting "news" and "articles" into normal content tree ** !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif!\[Ann-Patrice\] make forms for "news" and "articles" ** \[Steve\] scripts to export data & format into xml, ready to load ** \[Steve\] load data into alfresco, to be managed via webform * {color:#006600}*\[Steve\]*{color} {color:#000000}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){color} * {color:#006600}*\[Steve\]*{color} {color:#000000}Helpdesk questions:{color} ** {color:#006600}*\[Steve\]*{color} {color:#000000}what about Top 5? what is the requirement?{color} ** {color:#006600}*\[Steve\]*{color} {color:#000000}Help desk portal page - determine features, integration points{color} ** {color:#006600}*\[Steve\]*{color} {color:#000000}Find out how Help Desk Wiki will get articles into Alfresco{color} * {color:#006600}*\[Joe\]*{color} {color:#000000}make .htaccess emulation work for ordinary content{color} * {color:#ff0000}*\[Who?\]*{color} Testing: a simple smoke test to see if "build" is broken {dynamictasklist:Ann-Patrice} {dynamictasklist:Steve} {dynamictasklist:Joe} {dynamictasklist:Unassigned} |