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 "EclipseLink/Development/DevMeetings"
< EclipseLink | Development
(→Agenda - Oct 03 2007) |
|||
| Line 29: | Line 29: | ||
* Document requirements for check-in | * Document requirements for check-in | ||
* Remove deprecated packages and classes. ? | * Remove deprecated packages and classes. ? | ||
| + | |||
| + | == <i>Proposed</i> Agenda Oct 10th 2007 == | ||
| + | |||
| + | Testing strategy and layout for EclipseLink tests. Issues include: | ||
| + | * automated scripts | ||
| + | * ease of debugging failing tests | ||
| + | * which databasees? | ||
| + | |||
| + | == Minutes == | ||
| + | |||
| + | Coming soon | ||
Revision as of 16:18, 2 October 2007
Developer Meetings
Agenda - Oct 03 2007
Purpose: discuss milestones for Eclipse Persistence Services 1.0M1
- Automated Build
- Automated Test
- Testing on Open Source DB (Derby or MySQL)
- Document usecases that are expected to work
- about.html
- Initial component reorganization
- DBWS
- MOXy
- SDO
- EIS
- Small set of manual server tests
- Regular CTS run within Oracle
- IP Log accurate
- Build dependancies checked in (CDDL source files we depend upon
compiled to jars)
- Document "works with Oracle"
- How To Get Started Docs
- JPA
- MOXy
- SDO
- EIS
- Document how to build
- Document how to test
- Document requirements for check-in
- Remove deprecated packages and classes. ?
Proposed Agenda Oct 10th 2007
Testing strategy and layout for EclipseLink tests. Issues include:
- automated scripts
- ease of debugging failing tests
- which databasees?
Minutes
Coming soon