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"
< EclipseLink | Development
(→General Issues) |
|||
| Line 2: | Line 2: | ||
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 [https://dev.eclipse.org/mailman/listinfo/eclipselink-dev EclipseLink Dev mailing list]. | 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 [https://dev.eclipse.org/mailman/listinfo/eclipselink-dev 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 Nov 28, 2007 == | == Agenda Nov 28, 2007 == | ||
| Line 43: | Line 45: | ||
=== General Issues === | === General Issues === | ||
| + | * Adding JOTM to testing infrastructure to allow for JTA testing in unit tests. | ||
| + | * Checkin requirements for committers. | ||
| + | ** Committers should build all non extension components successfully. | ||
| + | * Generated artifacts (eclipselink.jar, installer.zip) should be removed from the repository | ||
* Slow Email Issue | * Slow Email Issue | ||
** For me it's gotten better but not perfect | ** For me it's gotten better but not perfect | ||
Revision as of 12:11, 29 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.
* 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 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
Dec 5th
- Automated build - Tom W
- Automated Testing - Tom W
- Publication of test results - Peter K
- no real update
- 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
- NOT DONE: Hosting the milestone Javadocs - Where to host? help? I can log in, exactly how to put it in.
- Foundation and JPA Status - Tom W
- OXM, JAXB, SDO - Blaise D
- Documentation Status - Rick S
- Ongoing. More than 120 pages currently available.
- Deprecation Removal - Kyle
- 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
- Adding JOTM to testing infrastructure to allow for JTA testing in unit tests.
- Checkin requirements for committers.
- Committers should build all non extension components successfully.
- Generated artifacts (eclipselink.jar, installer.zip) should be removed from the repository
- Slow Email Issue
- For me it's gotten better but not perfect
- 30-40 minutes rather than 2-4 hours.
- For me it's gotten better but not perfect
- 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 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.
- proposal for testing infrastructure - Mike N
- 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.