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.
EclipseLink/Development/DevMeetings
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 5, 2007
2PM EST, Wednesday November 28, 2007
Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546
Status updates
1.0M2
Dec 5th
- Milestone 2 to be built and put up today.
- 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
- Javadocs (Bug 210439) - Peter K
- DONE: Javadocs are building and being hosted on the downloads page nightly
- DONE: Downloads page to be redesigned to sub pages. see: www.eclipse.org/eclipselink/downloads
- DONE: Hosting the milestone Javadocs - M2 Javadocs Checked into CVS. found here http://www.eclipse.org/eclipselink/api/1.0/index.html. Will link from M2 page.
- Foundation and JPA Status - Tom W
- Deprecation Removal - Kyle
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
- Ongoing. More than 120 pages currently available.
- VERIFY: Target Milestone 1.0M2 - Please set all bugs closed in 1.0M2 to have target milestone of 1.0M2
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
- Checkin requirements for committers.
- Committers should build all non extension components successfully.
- Still required now that there is a continuous build?
- Committers should build all non extension components successfully.
- Bug Flow https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status
- How to handle? get QA involved?
- DONE: Generated installer.zip should be removed from the repository
- 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
- SVN Tagging of milestones and releases - Shaun/Tom
- bug created: 211759
- Development process: Email announcements - Doug
- Usage of the dummy email inboxes per components. You can register interest to get notified for all bugs of a given component
- Mailing lists: eclipselink.<component>-inbox@eclipse.org. You can register interest on your bugzilla preferences->email
- When you assign a bug to yourself please add the dummy inbox to the cc list
- Can we leverage this style of email announcement instead of eclipselink-dev. We could then use the dev mailing list to announce major new features or the start of projects and it is then up to interested parties to add themselves to the specific bug's cc list or ensure they are getting component bug notifications.
- Auto generation of backlog list from bugs.
Upcoming Issues
The following items require discussion but are not yet at the stage where a solution can be proposed.