Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/DevMeetings"
m (→1.0M3) |
(→1.0 Exit Criteria) |
||
| Line 44: | Line 44: | ||
==== 1.0 Exit Criteria ==== | ==== 1.0 Exit Criteria ==== | ||
| − | * | + | * 1.0 [[EclipseLink/Development/Release/1.0#1.0_Release_Criteria | Exit Criteria]] now documented. Please review and provide feedback on the dev mailing list - Doug |
| − | * Need to provide projected release date | + | * Need to provide projected release date. Planning for first half of 2008. Waiting for JAXB 2.1 compliance estimates - Doug |
=== General Issues === | === General Issues === | ||
Revision as of 16:13, 18 December 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.
* When adding agenda items please send an email to the eclipselink-dev@eclipse.org list notifying attendees. This will ensure attendees are aware of agenda items prior to the meeting.
Agenda Dec 12, 2007
2PM EST, Wednesday December 12th, 2007
Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546
Status updates
1.0M2
- Complete. Release Notes
1.0M3
- Proposed delivery date: January 8th, 2008
- Goal
- Complete removal of deprecated code? Is this feasible?
- 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?
- Dynamic Persistence Started
- Migration started
- OSGi started
- Automated build - Tom W
- Continuous builds - Action item: Peter to investigate continuous build
- Simple continuous build up and running (V1.0)
- compiling only (No automated tests running)
- email sent to dev list if the build fails. info sent in the email.
- Build kicked off every halfhour on the halfhour between 6:00am and 8:00pm. No change detection
- Simple continuous build up and running (V1.0)
- Continuous builds - Action item: Peter to investigate continuous build
- Automated Testing - Tom W
- JPA Tests run, some failures - Core tests hang
- Publication of test results - Peter K
- Foundation and JPA Status - Peter K
- Deprecation Removal - Kyle
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
- Complete User's Guide available. Minor/final cleanup remaining.
- Adding crosslinks from/to examples, FAQs, etc.
- Working on Contributor Guidelines
1.0 Exit Criteria
- 1.0 Exit Criteria now documented. Please review and provide feedback on the dev mailing list - Doug
- Need to provide projected release date. Planning for first half of 2008. Waiting for JAXB 2.1 compliance estimates - Doug
General Issues
- nightly eclipselink.jar checked into build -
- bug created: 211760
- new Productname EPS(EclipseLink) may be causing issues with our meta data
- Bugs button is now greyed out, and I can't figure out how to fix it. Escape brackets???
- Using EclipseLink in Equinox update - Shaun
- Auto generation of backlog list from bugs.
- Like to try this for M3. Peter to follow up
Upcoming Issues
The following items require discussion but are not yet at the stage where a solution can be proposed.
- EclipseLink/Development/Examples: Strategy for the development and maintenance of examples
- EclipseLink/Development/OSGi: Strategy for delivery of OSGi/Equinox bundles
- EclipseLink/Development/JPA_2.0: Strategy for the concurrent development of JPA 2.0 while maintaining JPA 1.0 usage
- EclipseLink/Development/Spring: Strategy for using EclipseLink within the Spring Framework