Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Milestone 1.0M9"
(→Components) |
|||
Line 2: | Line 2: | ||
* '''Revised Date July 27''' | * '''Revised Date July 27''' | ||
* '''Revised Date August 13''' | * '''Revised Date August 13''' | ||
+ | * '''Revised Date September 17''' | ||
Focus is: | Focus is: |
Revision as of 18:49, 24 August 2007
- Original Date June 15
- Revised Date July 27
- Revised Date August 13
- Revised Date September 17
Focus is:
- Finalize/freeze the architecture --all major interfaces defined and implemented
- Nightly automated builds for all components
- Improved deployment build documentation
Cross Cutting Concerns
Architecture
The expectation is that 1.0M9 (formerly "M0.9") represents finalized architecture for 1.0. (i.e. there will be no new component-level interfaces, etc.)
- IdAS Registry - finalize design
- CardStoreStrategy - finalize design
- Embedded CardManager - finalize design
Deployments
- H3 issues (we're trying to get as many as possible of these done for the June Catalyst demo)
- Can import MSFT CardSpace format personal cards (.crds files)
- Need a user friendly way of importing a .crd file --e.g. double click on .crd file
- Requires installation of tomcat (unacceptable complexity)
- Total size too large at approx 50+ MB
Components
Each Component owner should add a link to the 1.0M9 "to do list" for their component:
- HBX
- I-Card Manager
- RPPS Web app
- RPPS Core
- ISS
- Token Service TS ToDo
- IdAS: IdAS 1.0M9 tasks
- IdAS JNDI CP
- IdAS Jena CP