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
(→QA) |
|||
| Line 24: | Line 24: | ||
| − | == Agenda July | + | == Agenda July 22, 2010 == |
| − | [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=1&year=2010&hour=11&min=0&sec=0&p1=188 11 am EST, Thurs July | + | [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=1&year=2010&hour=11&min=0&sec=0&p1=188 11 am EST, Thurs July 22, 2010] |
=== Ad Hoc === | === Ad Hoc === | ||
| − | + | ** Process topic of contribution log - Please make sure all new code in 2.1.1 has proper header and dates | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ** Process topic of contribution log - Please make sure all new code in 2.1 has proper header and dates | + | |
| − | + | ||
== Release Planning == | == Release Planning == | ||
* 2.1.1 | * 2.1.1 | ||
| − | ** | + | ** Friday July 23 - code freeze |
* 1.2.1 | * 1.2.1 | ||
** requests to shut this down... | ** requests to shut this down... | ||
* 2.0.3 | * 2.0.3 | ||
| − | ** June/July | + | ** June/July ?? |
* Future Release Planning starting | * Future Release Planning starting | ||
| Line 119: | Line 112: | ||
== JPA == | == JPA == | ||
| − | + | July 22 2010: | |
| − | 2.1. | + | 2.1.1 |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* Bug Fixes | * Bug Fixes | ||
| + | ** Close down of bugs | ||
| + | ** Bug defferal | ||
== DBWS == | == DBWS == | ||
Revision as of 10:55, 22 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
- Friday July 23 - code freeze
- 1.2.1
- requests to shut this down...
- 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 16-22, 2010:
- Nightly Results
- trunk - 1 new failure in core-srg (probably intermittent) - investigating
- 2.1.1 - no new issue (the last build is 2010-07-21)
- 2.0.3 - no new issues (the last build is 2010-07-19)
- 1.2.1 - no new build (the last build is 2010-06-29)
- 1.1.4 - no new build (the last build is 2010-06-16)
- Testing
- DBWS util tests for Oracle database failed to run, filed 320308 -- fixed in build process
- SDO 2.1.1 TCK for main/2.1 - 2 failures - 320412 fixed
- Completed manual db cert testing
- Test Dev 2.2/2.1.1
- Fetch Group test dev - 100% , all fetchgroups testing are now running nightly on WLS, WAS. JBoss, Glassfish
- Reviewed and targeted bugs for 2.1.1
- Test Infrastructure
- Enhancements to test fwk to support testing multiple persistence units -- currently the cacheable tests use Multiple PUs, but we need to investigate if it is working as expected" - 80%
- Found several issues, currently fixing.
- Enhanced the feature - "Automatically kill overdue process and send out an email alert" - 100%
- Updated MySQL to 5.1.48
- Reviewed current JDBC driver versions used in testing -- plan to upgrade to latest versions
- Enhancements to test fwk to support testing multiple persistence units -- currently the cacheable tests use Multiple PUs, but we need to investigate if it is working as expected" - 80%
- Bugs
- Filed
- 320504 jpa.fetchgroups.SimpleSerializeFetchGroupTests.simpleSerializeAndMerge failed on WAS
- Fixed
- 319134 FetchGroups testsuite should run on application servers
- 290314 13 JPA2.0 tests in Advanced test suite shouldn't run on current JBoss version
- 290264 six new test in jpa.jpql.JUnitJPQLComplexTestSuite failed on JBoss
- 320504 jpa.fetchgroups.SimpleSerializeFetchGroupTests.simpleSerializeAndMerge failed on WAS
- Filed
- This week
- Multiple Persistence Units
- osgi/Gemini investigation (testing focus)
- Test on SQL Server 2008 R2
- fix bugs - 304227
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.2
- Target DBWS support for Glassfish, JBoss, Websphere
- Created a OSGi fragment bundle which a user can drop into Glassfish to access DBWS runtime services.
- DBWS bnd file being generated by EclipseLink build process
- JBoss, WAS support complete in 2.1.1
- Sparse Merge Support
- EclipseLink2.2 goals reviewed with PM
- 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
- Provide full support through external metadata file and annotations.
- MOXy External Metadata support
- Identify entries in deployment.xml that are currently not represented in external XML file.
- MOXY Dynamic Persistence
- Provide ability to bootstrap from external MOXy XML file
- SDO Server testing
- Running automated SDO server tests against JBoss, WAS, WLS app servers.
- 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.)