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 Nov 21, 2007) |
(→Agenda Nov 21, 2007) |
||
Line 10: | Line 10: | ||
* M2 Status | * M2 Status | ||
** Automated build - Tom W | ** Automated build - Tom W | ||
+ | *** Publication of nightly builds - Peter K | ||
+ | ** Automated Testing - Tom W | ||
+ | *** Publication of test results - ? | ||
** Foundation and JPA Status - Tom W | ** Foundation and JPA Status - Tom W | ||
** OXM, JAXB, SDO - Blaise D | ** OXM, JAXB, SDO - Blaise D |
Revision as of 17:21, 14 November 2007
Agenda Nov 21, 2007
2PM EST, Wednesday November 21, 2007
Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546
Status updates
- M2 Status
- Automated build - Tom W
- Publication of nightly builds - Peter K
- Automated Testing - Tom W
- Publication of test results - ?
- Foundation and JPA Status - Tom W
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
- ER 200040: New XSD for metadata: Need agreement on goals, benefits, and risks/issues - Guy P.
- Automated build - Tom W
General Issues
- Packaging of EclipseLink as plugings, Maven, ... - Wayne Beaton
Minutes from Past Meetings
Minutes Oct 17th 2007
Purpose: Discuss Testing strategy for EclipseLink tests.
- ChrisD, MikeN - what we've done so far ...
- brief discussion of strategy
- short-run goal: understand scope of testing requirements with view to reduce number of frameworks
- long-run goal: propose consolidated test framework plus migration of existing tests
- Action Items
- MikeN, ChrisD - put together a 'straw-man' proposal for consolidated test framework based on current understanding of testing requirements
Minutes 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. ?
Minutes: September 26, 2007
- Moving toward a 1.0 Release
- Timebox M1 vs making it feature rich
- Milestones should match 4 week sprint.
- Sprint Goal - 1.0M1 release
- First milestone is Nov 5th.
- Publish testing status
- Testing on Open Source DB
- MySQL
- Testing on Open Source DB
- Document usecases that are expected to work
- JPA
- MOXy (Native OXM - JAXB, SDO postponed to future sprint)
- Native ORM
- Supporting migration from TopLink 10.1.3, 11g
- Package renamer on client source
- Investigate reading in 10.1.3, 11g metadata
- Full Testing story
- Requirements for automated testing
- Automated Build
- Having all the jar files checked in
- Oracle Strategy to check in classfiles that reference Oracle Classes
- Build.xml
- get a cron job run on the EclipseServer
- Consumer Focused Collateral
- about.html
- Story for Derby - what tests are expected to pass
- Action Items
- Managers: number of available resources - deadline Oct 4th
- Managers and Dev team: Build task list
- Dev team: break above into tasks - deadline Oct 4th
- SprintPlanning Meeting: Friday Oct 5th
- Managers: number of available resources - deadline Oct 4th