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"
(→1.0 Release) |
|||
Line 14: | Line 14: | ||
* Bug Updates: | * Bug Updates: | ||
** [http://wiki.eclipse.org/EclipseLink/Development/Bugs Bug Queries and other useful links] | ** [http://wiki.eclipse.org/EclipseLink/Development/Bugs Bug Queries and other useful links] | ||
− | ** Open for 1.0: | + | ** Open for 1.0: 64 |
− | ** | + | ** 27 Opened this week. |
− | ** | + | ** 48 closed this week |
+ | *** eight in M9???? others are 1.0, M8, untarget | ||
+ | *** Solution? | ||
* Bug DB usage | * Bug DB usage | ||
Line 38: | Line 40: | ||
* Runtime Project | * Runtime Project | ||
+ | ** ONGOING | ||
** Move EclipseLink to runtime project. | ** Move EclipseLink to runtime project. | ||
** Keep history except for newsgroups. | ** Keep history except for newsgroups. | ||
Line 52: | Line 55: | ||
*** Found and fxed some build xml files. | *** Found and fxed some build xml files. | ||
− | ==== 1. | + | ==== 1.0M9 ==== |
− | * Milestone release Date - June | + | * Milestone release Date - June 18 2008 |
− | * | + | ** 8 Open bugs - please review |
− | * | + | ** 8 fixed |
* Foundation and JPA Status | * Foundation and JPA Status | ||
− | |||
− | |||
* OSGi - Tom | * OSGi - Tom | ||
− | ** | + | ** Wiki - http://wiki.eclipse.org/EclipseLink/Development/EclipseLinkPDEConversionPlan |
+ | ** PDE Projects available, eclipselink plugins in maven and jar containing all plug-ins available for download | ||
+ | ** Dynamic weaving in Equinox work underway | ||
+ | ** Initial planning for testing underway | ||
+ | ** Discussion | ||
+ | *** Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit) | ||
+ | **** Do we want a src and bin/classes directory | ||
+ | **** Should classes just exist at the base of the project (what about the jar we eventually create) | ||
+ | **** How should we name the jars we create | ||
* Workbench | * Workbench | ||
** Tested XML and EIS mapping functionality. | ** Tested XML and EIS mapping functionality. | ||
Line 70: | Line 79: | ||
* Documentation Status - Rick S | * Documentation Status - Rick S | ||
** Complete [[EclipseLink/UserGuide|User's Guide]] available. Minor/final cleanup remaining, as needed. | ** Complete [[EclipseLink/UserGuide|User's Guide]] available. Minor/final cleanup remaining, as needed. | ||
+ | ** Discussion | ||
+ | *** Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit) | ||
+ | **** Do we want a src and bin/classes directory | ||
+ | **** Should classes just exist at the base of the project (what about the jar we eventually create) | ||
+ | **** How should we name the jars we create | ||
==== 1.0 Release ==== | ==== 1.0 Release ==== | ||
* [[EclipseLink/Development/Release/1.0#1.0_Release_Criteria | Exit Criteria]] | * [[EclipseLink/Development/Release/1.0#1.0_Release_Criteria | Exit Criteria]] | ||
** 1.0M8 June 4, 2008 Final functionality freeze | ** 1.0M8 June 4, 2008 Final functionality freeze | ||
− | ** 1.0RC1 June | + | ** 1.0RC1 June 18, 2008 Release Candidate 1 |
− | ** 1.0RC2 June | + | ** 1.0RC2 June 25, 2008 Release Candidate 2 |
** 1.0 Release July 9, 2008 Final 1.0 Release (moved from june 25th to be released after Ganymede) | ** 1.0 Release July 9, 2008 Final 1.0 Release (moved from june 25th to be released after Ganymede) | ||
** Schedule Dependencies | ** Schedule Dependencies | ||
*** Eclipse reviews: graduation, release, and move to RT | *** Eclipse reviews: graduation, release, and move to RT | ||
*** Ganymede to leverage Equinox 3.4 (June 25) | *** Ganymede to leverage Equinox 3.4 (June 25) | ||
− | |||
− | |||
− | |||
* Pre-release tasks | * Pre-release tasks | ||
** 3rd party works-with approval for Oracle JDBC - Doug | ** 3rd party works-with approval for Oracle JDBC - Doug | ||
Line 92: | Line 103: | ||
** Finalize product packaging and distribution - ZIP(s), Bundle access (update site?) | ** Finalize product packaging and distribution - ZIP(s), Bundle access (update site?) | ||
** Prepare and schedule reviews | ** Prepare and schedule reviews | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
=== General Issues === | === General Issues === |
Revision as of 13:50, 11 June 2008
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 June 11 2008
2PM EST, Wednesday June 11, 2008
Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546
Status updates
- Bug Updates:
- Bug Queries and other useful links
- Open for 1.0: 64
- 27 Opened this week.
- 48 closed this week
- eight in M9???? others are 1.0, M8, untarget
- Solution?
- Bug DB usage
- If you are working on a bug, assign it to yourself.
- add dummy inbox to the cc list.
- Set the target milestone to the correct milestone.
- Confusion/concern on this part
- Milestones
- 1.0M9 are bugs that are to be fixed by the the corresponding milestone build.
- 1.0 is a bug that is to be fixed by 1.0, but has no current target milestone.
- 1.0.1 new bugs should be filed against this target
- If you are working on a bug, assign it to yourself.
- Bug council
- Introduce notion of Bug council
- Wed 2:30pm
- Untargeted bugs are going to be reviewed by bug council on a weekly basis (current proposed time is directly after weekly status meeting (2:30 ET on Wednesdays).
- A milestone will be set - or set to future
- Bug may get assigned
- When you enter a new bug, leaving it untargeted means that the bug council will review to decide which release it is targeted for.
- If you know which milestone the bug will be fixed in, assign it accordingly.
- The new target - future - is for bugs that don't have a target yet.
- Untargeted bugs are going to be reviewed by bug council on a weekly basis (current proposed time is directly after weekly status meeting (2:30 ET on Wednesdays).
- Runtime Project
- ONGOING
- Move EclipseLink to runtime project.
- Keep history except for newsgroups.
- Target right after M8
- Community
- Eric Gwin
- New committer! Thanks for voting
- Eric Gwin
- Code headers
- Ensure Header is dual license EDL + EPL
- Found and fxed some build xml files.
- Ensure contributor is correct - new code should have code author (no - intial code from oracle)
- Found and fxed some build xml files.
- Ensure Header is dual license EDL + EPL
1.0M9
- Milestone release Date - June 18 2008
- 8 Open bugs - please review
- 8 fixed
- Foundation and JPA Status
- OSGi - Tom
- Wiki - http://wiki.eclipse.org/EclipseLink/Development/EclipseLinkPDEConversionPlan
- PDE Projects available, eclipselink plugins in maven and jar containing all plug-ins available for download
- Dynamic weaving in Equinox work underway
- Initial planning for testing underway
- Discussion
- Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit)
- Do we want a src and bin/classes directory
- Should classes just exist at the base of the project (what about the jar we eventually create)
- How should we name the jars we create
- Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit)
- Workbench
- Tested XML and EIS mapping functionality.
- Able to open of toplink mapping workbench 10.1.3 projects
- Corrected the issue with Cache Synchronization (replaced functionality erroneously removed)
- MOXy, JAXB, SDO - Blaise D
- DBWS - Mike N
- Build System
- Documentation Status - Rick S
- Complete User's Guide available. Minor/final cleanup remaining, as needed.
- Discussion
- Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit)
- Do we want a src and bin/classes directory
- Should classes just exist at the base of the project (what about the jar we eventually create)
- How should we name the jars we create
- Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit)
1.0 Release
- Exit Criteria
- 1.0M8 June 4, 2008 Final functionality freeze
- 1.0RC1 June 18, 2008 Release Candidate 1
- 1.0RC2 June 25, 2008 Release Candidate 2
- 1.0 Release July 9, 2008 Final 1.0 Release (moved from june 25th to be released after Ganymede)
- Schedule Dependencies
- Eclipse reviews: graduation, release, and move to RT
- Ganymede to leverage Equinox 3.4 (June 25)
- Pre-release tasks
- 3rd party works-with approval for Oracle JDBC - Doug
- COMPLETE IP Log - Peter
- Complete Features Index - Doug with support of all committers
- Complete Examples & How-to materials - Doug/Shaun
- FAQ
- Update wiki Documentation for 1.0 Features - Liza (starting in May) with committer support
- Finalize product packaging and distribution - ZIP(s), Bundle access (update site?)
- Prepare and schedule reviews
General Issues
- WIKI Changes should be done in parallel to any bug fixes to eclipselink.*.test ant targets or other public API changes - mobrien 20080529.
- DONE Bugzilla components - sign-off on final changes below
http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00640.html
- Automated Testing
- Need SRG test models for JPA, MOXy and SDO
- DB components of those tests should be simple enough to run on Derby
- Need to test Core SRG on Derby
- Need SRG test models for JPA, MOXy and SDO
- Bug Prioritization and targetting
- Currently more bugs are scheduled for 1.0.1 then we are likely to fix in that time
- We currently do not have a system to ensure a bug has a published priority level
- We should discuss how will we deal with these issues
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
- EclipseLink/Development/Java6: Strategy for using EclipseLink on a Java SE 6 JRE
Minutes from Past Meetings
- May 21, 2008 - No Meeting
- May 14, 2008
- May 7, 2008
- April 30, 2008
- April 16, 2008
- April 9, 2008
- Feburary 27, 2008
- Feburary 20, 2008
- OSGi Demo on Feburary 13, 2008
- January 30, 2008
- January 23, 2008
- January 16, 2008
- January 9, 2008
- December 19, 26, 2007, January 2, 2008 - cancelled
- December 12, 2007
- December 5, 2007
- November 29, 2007
- November 21, 2007
- November 14, 2007
- November 7, 2007
- October 31, 2007
- Previous minutes