To do for Tapestry Migration
Collect ContributorLicenseAgreements - ?
- Howard Ship - Yes
- Geoff Longman - Yes
- Malcolm Edgar - Yes
- ...
- Review distribution for L/GPL issues
- Possible outstanding issue in linkage to GPL McKoiDB (for demos)
- Add Apache License to source (is v2 license available?)
- Done - HLS - Created script to automate updating licences (when v2 is available, for instance)
Fix web site to provide a link to Jakarta, not SourceForge.
- Done - HLS - In the 2.3-rc-1 build
Big rework of web site to match Jakarta style. [Forrest or Maven?]
- Did an initial change to match colors a bit better, much more to do - HLS
- Ensure build produces binary and source distributions
- Done - HLS
- Get nightly builds happening - gump?
- Put togther a release as a first milestone to allow people to convert to the new package structure and to have a release available for download in the site wide bin area.
- Migrate/setup Wiki
- Archive mailing lists
- Done
Add Tapestry to BugZilla [Have you thought about adding it to Scarab?]
Setup MoinMoin Wiki for Tapestry
Is Done for Tapestry Migration
Set up mailing lists - Done - SamRuby
Set up cvs module - Done - SamRuby, AndrewCOliver
- Integrate private branch changes
- Branch hship-2-3 done which is most of the cool stuff - HLS
Branch mb-2-3 still waiting for Mind Bridge - MB has been absent for a bit, I think his changes will need to be redone in the context of the latest codebase
Note mail lists on the appropriate website - Done - DionGillard
- Set up website on daedalus
- done - ACO
- we should move this to Gump once Tapestry is set up on gump.
Notes and stuff
I would suggest regardless of how nightly builds are run, that Tapestry integrate via Gump. Its just good technical sense and helps integrate with the rest of the Apache community. -Andy
Non setup-related
- Get Tapestry demos working with latest stable JBoss, 3.0.4
- Done - HLS