Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] Minutes: committer meeting April 8th

== Agenda Apr 8, 2010  ==
[ 11 am EST, Thurs Apr 8, 2010]

=== Ad Hoc ===
* EclipseLink Summit:

== Release Planning ==
* 2.0.2: Proposed date: April 21st\
** Stream is now frozen.  Showstoppers approved by Doug/Peter only.
* [ 2.1] [[Helios]]

== QA ==

April 2 - April 8, 2010:

* Nightly Results
** 1.1.4 - clean
** 2.0.2 - no recent builds
** 1.2.0 - no recent builds
** trunk - 1 new FL failure - investigating; 1 test failed JPQL on PostGreSQL - bug entered
* Last week
** Fixed Bugs
*** 307771 -  JBoss EAP server couldn't be stopped properly 
** Ran WDF tests in JBoss - passed; reviewed test code - additional changes required to remove hardcoding tx type, ds type, ds name, etc...
** EL 2.1 Advanced Query
*** FUNC support test spec 100% - reviewed by Dev
*** Downcast - documents reviewed, reviewed example
** JAXB nightly tests - email notification now working
** JAXB 2.2 - now running every other night
** EL 2.1 Advanced JPA Config - reviewed feature docs, and the tests that have been added - only Fetch group needs to be reviewed.
** JPA/JBoss EAP - now running nightly
** Triage - 2 bugs filed
*** Investigated EclipseLink 1.1.4 GlassFish V2 test failures
*** JPA LRG hanging issue on trunk... intermittent
* This week
** WDF - after changes checked in, will run on WebLogic Server and Websphere.
** Triage results from JAXB 2.1 and 2.2 TCK and enter bugs
** Continue with EL 2.1 test dev work - Advanced querying, Advanced JPA config
** Fix Bugs
*** 287222  -  All new added JPA 2.0 tests need to be modified to run on JPA 2.0 servers
*** 293614  -  JPA 2.0 Cacheable Test Suite need to be enabled for JPA 2.0 servers
** JAXB osgi testing - investigation

== Build ==
* Milestone Releases
** M6 EclipseLink
** M6 Helios contribution (nightly build)
*** Due to an uncaught bug found by the Helios build system.
*** We need to modify our milestone strategy. Milestones should be promoted *after* the Helios contribution is made. 
* "target platform" work for Helios (bug 306188)
** RT is requesting we simplify how we are included in RT - siingle SDK
*** the one feature can and should simply include our other already existing features.
* As of M6 EclipseLink is no longer shipped with the Java EE Package
** As a team we need to decide:
*** What we should offer regarding IDE tooling that helps the developer use EclipseLink
*** If we should help another team provide it (Dali ?)
* Helios build integration (293034) (Blocked until Post M6)
** Need to do p2 consolidation work to manage multiple versions in a single update location.
*** investigation composite repositories
**** Have working prototype. 
**** Working on creating a Composite of all our releases - (completed locally).
***** Cannot generate on Download machine due to bug 303802 fix will be available in M6 helios release.
**** Still need to finalize automation.
***** Automation for Composite work still pending. Looks like a separate script will be necessary.
*** Migration from p2.metadata.generator to p2.publisher (Blocked by bug 303802).
**** Prototype complete. 
***** Awaiting confirmation of a bugfix before commit (Blocked by bug 303802).
***** Still need to finalize automation (Blocked by bug 303802).
* 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).
* 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% 

Fixed Bugs:

== JPA  ==
April 2 - April 8, 2010:

* no bugs
** two bug fixes waiting on reopen of stream
*** Exteranious logging
*** Blob/Clob Length
* Advanced JPA config
** Dynamic persistence 
* Advanced JPA Querying
** Downcast queries implementation
** Fetch Group
* Bug Fixes
** Cache evict
** Native Case sensitivity

== DBWS  ==
[ DBWS Development]

* No remaining bugs
* Providing release note for issue when deploying DBWS war file to container in a JRockit VM.  This can be worked around by building war in IDE, rather than depending on ASM to code-generate DBWSProvider.class file.

* 290156 Validate SOAP message elements
* Scoping out potential EclipseLink feature work
** Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)

== SDO / MOXy  ==
* All 2.0.2 bugs resolved

* Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format [ Design]
* MOXY Dynamic Persistence [ Design]
** Phase 7 of development complete
** Runtime dependency introduced on JAXB XJC (Schema-to-Java compiler).  Issue creating plugin project for XJC library - may need to deliver MOXy dynamic persitence as a regular Java project (ie. would not be available through OSGi).
** Phase 8 introduces enum support - will need core Dynamic Persistence support.
* JAXB2.2 Compliance
** Down to one failing test - a TCK challenge has been issued against this.
* OSGi, Server testing
** Discussion with Dev, QA teams to improve the level of server and OSGi testing we have for MOXy and SDO components.

== Dynamic Persistence ==
[ Dynamic Persistence]

== EclipseLink Incubator  ==

* [[EclipseLink/Development/Incubator/Extensions]]
** NetWeaver platform promotion.

== 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 [ 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.

Back to the top