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"
(→SDO / MOXy) |
m (→Bug Status) |
||
(One intermediate revision by the same user not shown) | |||
Line 139: | Line 139: | ||
*** Doug requesting help. | *** Doug requesting help. | ||
** Please provide feedback on [[EclipseLink/Development/Incubator/Extensions/DatabasePlatformPromotion | Proposal for lowering barrier of entry for new database platforms]] | ** Please provide feedback on [[EclipseLink/Development/Incubator/Extensions/DatabasePlatformPromotion | Proposal for lowering barrier of entry for new database platforms]] | ||
+ | |||
+ | == Documentation == | ||
+ | *Working on automated doc build process (Rick & Eric)<br />If not possible, Rick is working on an automated localized doc build process, and would simply post the daily doc builds | ||
+ | *Updated [http://wiki.eclipse.org/EclipseLink/Development/Documentation/Requirements Documentation Requirements and Build Proposal] | ||
+ | *Several "chapters" currently stored in XML. More to come once the production/build process is finalized. | ||
+ | *Need discussion about how the strategy we are using for User Documentation compares to the wiki-based strategy we are using for developer documentation and whether there is merit to changing the way we do developer documentation. This discussion should wait until we have used found all the issues with our User Documentation Strategy. | ||
+ | |||
== Bug Status == | == Bug Status == |
Revision as of 10:40, 25 February 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 Feb 4, 2010
Ad Hoc
- Need discussion about how the strategy we are using for User Documentation compares to the wiki-based strategy we are using for developer documentation and whether there is merit to changing the way we do developer documentation. This discussion should wait until we have used found all the issues with our User Documentation Strategy.
Release Planning
- 1.1.4: Not yet scheduled - Planned final patch for 1.1.x stream
- wait for community to request.
- 2.0.1: Released Feb 17th
- 2.0.2: Proposed date: April 21st
- 2.1 Helios
- Galileo SR2 - February 26th/2010
- RC1+0 Jan 18/10: EclipseLink 1.1.3 (latest Milestone or Release)
- 1.1.3 has been put into SR2
- RC1+0 Jan 18/10: EclipseLink 1.1.3 (latest Milestone or Release)
QA
Feb 12 - 18, 2010:
- Last week
- Monitor and triaged nightly tests:
- 1.1.4 - good
- 2.0.1 (RC1) - WAS Oracle custom features tests failed - fixed; SQL Server 2008 nightly hanged - dev in progress (manual run passed)
- 1.2.0 - good
- trunk - DBWS examples on WLS didn't run properly - investigating
- EL 2.0.1 testing - 100%
- WDF - add tests to nightly runs - completed - passing
- Pessimistic Locking Extended Scope - test implementation - complete, patch sent for review
- MOXY - worked with dev on JAXB testing - fix existing failures
- Investigated JPA TCK, DBWS test failures
- Misc test infra fixes/enhancements
- Monitor and triaged nightly tests:
- This week
- Review high priority work for 2.1, infrastructure work
- Test infra - switch between datasource types, weaving types, EM (app managed, container managed) --> need to backport to 2.0.x stream.
- Fix Bugs
- Backlog
Build
- Milestone Releases
- 2.0.1 RC1
- Test component build cleanup (Holding)
- Restructure to allow testing to *not* rebuild product jars (293032)
- Will use "static targets" as discussed in meeting last week (297217).
- Tests will not compile when run target called.
- merged partial work to update standards.
- migration work for test projects, currently priority 2
- Need shippable testing artifacts (R2).
- Restructure to allow testing to *not* rebuild product jars (293032)
- Helios build integration (293034)
- Need to do p2 consolidation work to manage multiple versions in a single update location.
- investigation composite repositories
- currently determining if existing ant tasks designed for use within Eclipse can be utilized externally.
- Need to do p2 consolidation work to manage multiple versions in a single update location.
- jpa.test10 Suite - Holding
- Explore possibility of using eclipselink.jpa.test from 1.1.3 as a way to certify javax.persistence 1.0 backward compatability in EclipseLink 2.0.x
- All tests now compiling with trunk, 83% success rate on Test run.
- Awaiting review by Tom or Peter of test results (still).
- Need "project name" assuming this gets running 100%
- Explore possibility of using eclipselink.jpa.test from 1.1.3 as a way to certify javax.persistence 1.0 backward compatability in EclipseLink 2.0.x
Fixed Bugs:
JPA
2.0.2 bug fixes. 2.1.0
- Advanced JPA config
- Fetch groups complete
- Additional Join investigation is next
- Advanced JPA Querying
- wiki started with prioritized feature list (http://wiki.eclipse.org/EclipseLink/Development/2.1/AdvancedJPA_Queries)
- Prototype of FUNCTION support in JPQL.
- available on bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=300512
- OSGi
- Investigation starting this week.
- WDF testing
- Tests run nightly
DBWS
2.0.2
- 303331 Currently throw NPE for PL/SQL procedure with argument defaults. Need to handle this more gracefully
2.1.0
- Scoping out potential EclipseLink feature work
- Support for advanced PL/SQL datatypes (records, collections, mixture of the two) as arguments to Stored Functions
- Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)
- DBWS (JAX-WS) support on multiple platforms (JBoss, WAS)
SDO / MOXy
2.0.2
- 301062 MOXy - JAXB: Issues with multiple XmlElementDecl with same QName and different scope
- 302481 Account for XMLStreamReader returning both null and "" for no namespace
- 303631 JAXB - incorrect date conversion from XMLGregorianCalendar with schemaType set to date
- 303692 JAXB - static final attribute fields are ignore during schema generation but should make fixed attributes
- 302167 XMLBinderBasicTests are failing with Oracle's Xmlparser
2.1.0
- Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
- MOXY Dynamic Persistence Design
- JAXB2.2 Compliance
- JAXB2.2 CQs approved (API, RI, XJC).
- Blaise has been nominated as an Orbit committer, in readiness for contributing the JAXB2.2 binaries.
- Also need to submit JAXB2.1.12 jars to Orbit (CQs previously approved for Helios)
- JAXB2.2 CQs approved (API, RI, XJC).
- Continued improvements to MOXY marshalling/unmarshalling performance
Dynamic Persistence
- 303651 Issue raised on forum with dynamic entities not having their attribute-change-tracker properly setup after the first entity transaction commit call
EclipseLink Incubator
EclipseLink/Development/Incubation
- EclipseLink/Development/Incubator/Extensions
- FetchPlan incubator active
- Doug requesting help.
- Please provide feedback on Proposal for lowering barrier of entry for new database platforms
- FetchPlan incubator active
Documentation
- Working on automated doc build process (Rick & Eric)
If not possible, Rick is working on an automated localized doc build process, and would simply post the daily doc builds - Updated Documentation Requirements and Build Proposal
- Several "chapters" currently stored in XML. More to come once the production/build process is finalized.
- Need discussion about how the strategy we are using for User Documentation compares to the wiki-based strategy we are using for developer documentation and whether there is merit to changing the way we do developer documentation. This discussion should wait until we have used found all the issues with our User Documentation Strategy.
Bug Status
Foundation and JPA
Open Bugs
Date | 1.1.4 | 1.2.1 | 2.0 | 2.0.1 | 2.0.2 | 2.1 | Future/1.1.x | Untargetted |
---|---|---|---|---|---|---|---|---|
February 11, 2010 | 1 | 1 | x | 3 | x | 80 | 523 | 142 |
January 14, 2010 | 1 | 2 | x | 42 | x | 52 | 496 | 142 |
December 7, 2009 | 4 | 5 | 3 | 25 | x | 30 | 495 | 149 |
November 12, 2009 | 2 | 2 | 186 | 6 | x | x | 357 | 131 |
November 5, 2009 | 1 | 1 | 189 | 3 | x | x | 354 | 131 |
October 29, 2009 | 1 | 1 | 194 | x | x | x | 345 | 125 |
October 22, 2009 | 0 | 0 | 203 | x | x | x | 362 | 131 |
Resolved Bugs
Date | 1.1.x | 1.2.x | 2.0 | 2.0.x | 2.1 | Invalid | Duplicate | Submitted Patch |
---|---|---|---|---|---|---|---|---|
February 11, 2010 | 1 | 3 | x | 26 | 17 | 8 | 9 | 3 |
January 13, 2010 | 0 | 1 | 1 | 10 | 4 | 3 | 1 | 0 |
December 7, 2009 | 2 | 1 | 71 | 0 | 3 | 12 | 18 | 0 |
November 11, 2009 | 0 | 0 | 15 | x | x | 6 | 2 | 0 |
November 4, 2009 | 0 | 1 | 20 | x | x | 5 | 1 | 0 |
October 28, 2009 | 0 | 1 | 26 | x | x | 4 | 2 | 2 |
October 21, 2009 | 0 | 2 | 20 | x | x | 2 | 1 | 1 |
New Bugs
Date | 1.1.4 | 1.2.1 | 2.0 | 2.0.1 | 2.0.2 | 2.1 | Future | Enhancement | Already resolved |
---|---|---|---|---|---|---|---|---|---|
February 8, 2010 | 1 | 1 | x | 15 | 2 | 18 | 31 | 7 | 32 |
January 13, 2010 | 2 | 0 | x | 10 | x | 11 | 28 | 9 | 20 |
December 7, 2009 | 1 | 3 | 35 | 8 | x | 3 | 37 | 10 | 56 |
November 11, 2009 | 0 | 0 | 8 | 3 | x | x | 3 | 2 | 2 |
November 4, 2009 | 1 | 2 | 17 | 3 | x | x | 4 | 0 | 0 |
October 28, 2009 | 0 | 1 | 10 | x | x | x | 8 | 0 | 6 |
October 21, 2009 | 0 | 0 | 9 | x | x | x | 0 | 0 | 4 |