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 28, 2007) |
||
| Line 9: | Line 9: | ||
<b>Dial In Info: </b> 1-888-967-2253, Conf ID/Password: 486546/486546 | <b>Dial In Info: </b> 1-888-967-2253, Conf ID/Password: 486546/486546 | ||
| − | + | === Status updates === | |
| − | + | ==== 1.0M2 ==== | |
| − | + | * Automated build - Tom W | |
| − | + | * Automated Testing - Tom W | |
| − | + | ** Publication of test results - Peter K | |
| − | * | + | * [http;//bugs.eclipse.org/210439 Javadocs (Bug 210439)] - Peter K |
| − | + | * Foundation and JPA Status - Tom W | |
| − | + | * OXM, JAXB, SDO - Blaise D | |
| − | + | * Documentation Status - Rick S | |
| − | + | ||
| − | + | ||
| − | + | ==== 1.0M3 ==== | |
| + | * Proposed delivery date: January 8th, 2008 | ||
| + | * High Level Goals? | ||
| + | ** Complete removal of deprecated code? | ||
| + | ** Initial EclipseLink-ORM.XML XSD ([http://bugs.eclipse.org/200040 Bug 200040]) with bugs logged for additional XML and annotations | ||
| + | ** Automated testing using MySQL with published results? | ||
| + | ** Initial working version of Workbench? | ||
| + | |||
| + | ==== 1.0 Exit Criteria ==== | ||
| + | * Need to firm up 1.0 [[EclipseLink/Development/Release/1.0#1.0_Release_Criteria | Release Criteria]] | ||
| + | * Need to provide projected release date | ||
| + | |||
| + | === General Issues === | ||
| + | |||
| + | * Components: Confirm name changes prior to having webmaster make changes - Doug | ||
| + | ** Rename ORM to JPA | ||
| + | ** Rename OXM to MOXy | ||
| + | ** Add SDO | ||
| + | ** Add Utils | ||
| + | * Using EclipseLink in Equinox update - Shaun | ||
| + | * SVN Tagging of milestones and releases - Shaun/Tom | ||
| + | * Development process: Email announcements - Doug | ||
| + | ** Usage of the dummy email inboxes per components. You can register interest | ||
| + | ** | ||
| + | |||
| + | === Upcoming Issues === | ||
| + | |||
| + | The following items require discussion but are not yet at the stage where a solution can be proposed. | ||
== Minutes from Past Meetings == | == Minutes from Past Meetings == | ||
Revision as of 14:38, 27 November 2007
The EclipseLink committers have a regular meeting (currently weekly) to discuss ongoing development issues and projects. All interested parties are welcome to attend. If you have any additional items you wished discussed please add them at the bottom of the agenda including a brief description and any relevant links. Alternatively development issues can be discussed on the EclipseLink Dev mailing list.
Agenda Nov 28, 2007
2PM EST, Wednesday November 28, 2007
Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546
Status updates
1.0M2
- Automated build - Tom W
- Automated Testing - Tom W
- Publication of test results - Peter K
- [http;//bugs.eclipse.org/210439 Javadocs (Bug 210439)] - Peter K
- Foundation and JPA Status - Tom W
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
1.0M3
- Proposed delivery date: January 8th, 2008
- High Level Goals?
- Complete removal of deprecated code?
- Initial EclipseLink-ORM.XML XSD (Bug 200040) with bugs logged for additional XML and annotations
- Automated testing using MySQL with published results?
- Initial working version of Workbench?
1.0 Exit Criteria
- Need to firm up 1.0 Release Criteria
- Need to provide projected release date
General Issues
- Components: Confirm name changes prior to having webmaster make changes - Doug
- Rename ORM to JPA
- Rename OXM to MOXy
- Add SDO
- Add Utils
- Using EclipseLink in Equinox update - Shaun
- SVN Tagging of milestones and releases - Shaun/Tom
- Development process: Email announcements - Doug
- Usage of the dummy email inboxes per components. You can register interest
Upcoming Issues
The following items require discussion but are not yet at the stage where a solution can be proposed.