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
| Line 37: | Line 37: | ||
** RC2 Aug 13th | ** RC2 Aug 13th | ||
* 1.1.4 | * 1.1.4 | ||
| − | ** | + | ** 10 bugs closed in 1.1.4 |
| + | ** No open bugs | ||
| + | ** RC1 - Aug 9th | ||
* 2.0.3 | * 2.0.3 | ||
** June/July ?? | ** June/July ?? | ||
Revision as of 10:42, 29 July 2010
Dial In Info:
- please contact Peter Krogh for dial in information.
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.
Call Schedule
The calendar is available in the following formats:
iCal,
ATOM News Feed,
HTML
Agenda July 22, 2010
11 am EST, Thurs July 22, 2010
Ad Hoc
- Process topic of contribution log - Please make sure all new code in 2.1.1 has proper header and dates
Release Planning
- 2.1.1
- RC1 Aug 5th
- RC2 Aug 13th
- 1.1.4
- 10 bugs closed in 1.1.4
- No open bugs
- RC1 - Aug 9th
- 2.0.3
- June/July ??
- Future Release Planning starting
- 2.2 - December 8th, 2010 - http://wiki.eclipse.org/EclipseLink/Development/2.2
- 2.2M1 - July 21
- 2.2M2 - August 19
- 2.2M3 - September 22
- 2.2M4 - October 20 - Functional Freeze.
- IPLog and Release docuware - end of October
- 2.2RC1 - November 3rd, 2010
- 2.2RC2 - November 17th, 2010
- 2.2RC3 - Novemeber 24th, 2010
- 2.2 Release - December 8th, 2010
- 2.3 (Indigo) - June 22nd, 2011 - http://wiki.eclipse.org/EclipseLink/Development/2.3
- 2.2 - December 8th, 2010 - http://wiki.eclipse.org/EclipseLink/Development/2.2
QA
July 23-29, 2010:
- Nightly Results
- trunk - 4 TC failed WLS JPA (fwk change issue, investigating)
- 2.1.1 - 1 TC WDF failed; bug filed
- 2.0.3 - no new build (the last build is 2010-07-19)
- 1.2.1 - ! TC static weaving - intermittent (the last build is 2010-07-2x)
- 1.1.4 - no new build (the last build is 2010-06-16)
- Testing
- SQL Server 2008 R2 - all passed
- Test Dev 2.2/2.1.1
- Multiple Persistence Units - test fwk changes reviewed and checked in
- Test Infrastructure
- Updated MySQL to 5.1.49 (re-imaged machine)
- Updated Derby DB to 10.6.1.0
- Reviewed current JDBC driver versions used in testing -- plan to upgrade to latest versions
- Bugs
- Filed
- Fixed
- This week
- Test fwk changes - avoid hard coding in WAS python scripts
- osgi/Gemini investigation (testing focus)
- EL 2.1.1 closedown
- fix bugs - closedown of 2.1.1
Build
- Milestone Releases
- none
- Custom Ant tasks to replace Javascript in build
- Was needed for SAP JVM testing
- EclipseLink Summit Items to review:
- Move to PDE build? (drop ant)
- Advantages: get many features now have to 'hack'
- Disadvantages: tied to someone else's process. May not work with our versioning. Web distributions, etc.
- If we decide to drop ant support will need to plan phase-out, and investigate PDE capabilities further.
- Investigation and prototyping in progress.
- Rename build.xml and build.properties (260428)
- what to rename to? antbuild? eclipselink? suggestions?
- will use antbuild.xml and antbuild.properties.
- what to rename to? antbuild? eclipselink? suggestions?
- Move to PDE build? (drop ant)
- Review process for build bugs?
- Future direction of build?
- Created Wiki page to capture open issues and help plan improvements.
- Future direction of build?
Fixed Bugs:
JPA
July 22 2010:
2.1.1
- Bug Fixes
- Close down of bugs
- Bug defferal
DBWS
2.1.1
- DBWS support on Glassfish, JBoss, Websphere
- Created a OSGi fragment bundle which a user can drop into Glassfish to access DBWS runtime services.
- DBWS bnd file now being generated by EclipseLink build process
- Testing DBWS in Equinox OSGi environment with Jetty
- Sparse Merge Support
- Building on top of Fetch Group feature introduced in EclipseLink2.1
SDO / MOXy
2.1.1
- No remaining bugs open for 2.1.1
- JBoss: Implemented a solution to detect a redeploy event using MBean notification listeners
- Will migrate to use full core MBean solution on these platforms in 2.2
2.2.0
- Targetting deprecation of existing MOXy deployment.xml
- http://wiki.eclipse.org/EclipseLink/DesignDocs/317962
- Phase 1 – MOXy annotation equivalent to XML metadata support
- Phase 2 – Annotations and XML Support for relevant ORM annotations
- Phases 1 & 2 targetted in Aug 20 sprint
- Phase 3 - Annotations and XML Support for relevant JPA annotations
- MOXY Dynamic Persistence
- Provide ability to bootstrap from external MOXy XML file
- Feature work: Platform integration
- Demo: Use EclipseLink JAXB when running JAX-RS RESTful web service (based on Jersey RI). Demonstrates ability to marshal to JSON as well as XML documents.
EclipseLink Incubator
EclipseLink/Development/Incubation
- EclipseLink/Development/Incubator/Extensions
- MaxDB work in progress
- Time to create separate sub-project for incubator
- Increase community of committers
- Try out GIT & eGit/jGit tooling in incubator?
Documentation
- New EclipseLink documentation plan: Documentation Requirements and Build Proposal
- Continuing to build/port JPA content to new JPA guide: [1]
- Need input/outline for additional guides (moxy, dbws, etc.)