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
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
− | |||
− | + | == Agenda Nov 14th, 2007 == | |
2PM EST, Wednesday November 14, 2007 | 2PM EST, Wednesday November 14, 2007 | ||
Line 33: | Line 32: | ||
* Utilities Component Sign Off - Doug C | * Utilities Component Sign Off - Doug C | ||
− | == Minutes from Past Meetings | + | == Minutes from Past Meetings == |
* [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00273.html November 7, 2007] | * [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00273.html November 7, 2007] | ||
* [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00255.html October 31, 2007] | * [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00255.html October 31, 2007] |
Revision as of 17:15, 14 November 2007
Agenda Nov 14th, 2007
2PM EST, Wednesday November 14, 2007
Dial In Info
Phone: 1-888-967-2253
Conf ID/Password: 486546/486546
Status updates
- M2 Planning
- M2 dates and targets - Doug C
- Automated build - Tom W
- Foundation and JPA Status - Tom W
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
- Initial review has been approved by Eclipse. Have begun cleaning/preparing wiki pages. The EclipseLink User's Guide will be posted (as pages are prepared) here.
- ER 200040: New XSD for metadata: Need agreement on goals, benefits, and risks/issues - Guy P.
- Publishing of internal design/architecture documents to assist committers and contributors in their understanding of Eclipselink - Doug C.
General Issues
- Dev Process
- Quick Dev Process review - Tom W
- Reminder: EclipseLink bugs should contain detailed information even if bug is also logged in another system
- Documented at: http://wiki.eclipse.org/EclipseLink/Development/Process
- Utilities Component Sign Off - Doug C
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