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"
(→QA) |
(→QA) |
||
Line 81: | Line 81: | ||
July 5-12, 2012: | July 5-12, 2012: | ||
− | * EclipseLink Nightly Results (Updated on 2012-07- | + | * EclipseLink Nightly Results (Updated on 2012-07-12) |
− | ** trunk - | + | ** trunk - most jpa-lrg failed on JRockit16 - bug: [384842|https://bugs.eclipse.org/bugs/show_bug.cgi?id=384842]; several new failures with jpa on h2 and Derby db - developer is working on it. (the last build is 2012-07-12) |
− | ** 2.4.1 - | + | ** 2.4.1 - no new issue (the last build is 2012-07-10) |
− | ** 2.3.4 - | + | ** 2.3.4 - 2 new failures with jpa on wls 10.3.6patch - seems to be intermittent, need to confirm. (the last build is 2012-07-11) |
* Testing | * Testing | ||
* Test Dev | * Test Dev |
Revision as of 10:47, 12 July 2012
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 June 14, 2012
Ad Hoc
Review of 2.4 Dev page:
http://wiki.eclipse.org/EclipseLink/Development/2.4.0
Please ensure that this page has tasks that are scheduled for 2.4.
Release Planning
- 2.3.4 - GA ??
- M1 - ??
- 2.4.1 - GA ??
- M1 - Jul 5
- M2 - Jul 18
- 2.5.0 - GA ??
- M1 - Jul 4 (Complete)
- M2 - Jul 18
- M3 - Aug 1
- Juno SR1 - Sept! (Milestone dates are when contibution is due)
- SR1-RC1+1 - Sept
Migration to Git
- Dev process FAQ
- Git demo (later)
- TBA
- Tortiose Git is available for Windows (Beta)
- Team transition may now be seemless (except for mavenization)
- when using putty should use "git.eclipse.org" as profile name
- Full test repo is available for testing at:
- Team transition may now be seemless (except for mavenization)
- Transition targeted for July
- Refresh of test Repo coming - late June
- Will contain "hanging" branches. (Only trunk is viable).
- Initial Internal repos targetted for availability third week of July to include:
- Normalized branches
- translated build labels
- stripped of binaries
- updated build for Git use (change in qualifiers)
- Once Internal prototype complete
- Dev to verify repositories
- Once verified will be given to webmasters for posting
- Once on site SVN will be made read-only, and newer transactions will need to be migrated.
- Refresh of test Repo coming - late June
- Status
- New copy of SVN repository
- Exported a dump, Normalized, and tested by creating local SVN repository.
- All looks ok.
- Getting intermediate dump from webmaster (to bring conversion up-to-date)
- will add to normalized dump.
- one tool failing to load dump for conversion
- another was successful, but still had issues.
- Git migration work continues today - post Juno release
QA
July 5-12, 2012:
- EclipseLink Nightly Results (Updated on 2012-07-12)
- trunk - most jpa-lrg failed on JRockit16 - bug: [384842|https://bugs.eclipse.org/bugs/show_bug.cgi?id=384842]; several new failures with jpa on h2 and Derby db - developer is working on it. (the last build is 2012-07-12)
- 2.4.1 - no new issue (the last build is 2012-07-10)
- 2.3.4 - 2 new failures with jpa on wls 10.3.6patch - seems to be intermittent, need to confirm. (the last build is 2012-07-11)
- Testing
- Test Dev
- Metadata caching feature completed -- reviewed feature with dev
- Test infrastructure
- Git development env setup
- Test Infra migration to Git - in progress
- ssh/http access to git from Windows/Linux
- scripts to clone/pull repositories to local env
- JPA automated testing support for JBoss 7 - in progress; can run most of the tests manually though. Filed bug [380670 | https://bugs.eclipse.org/bugs/show_bug.cgi?id=380670] \- dev reviewing
- Upgrade Spring to 3.1.1
- This week:
- Git Migration
- Metadata caching test spec
- Migration to Windows 7
- Oracle-specific DBWS test suite - needs infra changes
- JPA-RS for WebLogic
- DBWS tests on JBoss 7 (moved to backlog)
- Backlog:
- Add JBoss 7 to nightly testing
- DBWS tests on JBoss 7
- Investigating Enable JPA 1.0 TCK on GlassFish v3
- Review table-per-tenant functionality
- Add Open JDK certification tests
- Git migration
- Enable JPA 1.0 TCK on GlassFish v3
- 370988 - JAX-RS tests need to be separate project in order to avoid dependency issues in Eclipse IDE
- oracle specific tests failures on GlassFish - tried suggestions from dev, but not successful - on hold
- optimize setup/teardown of JAXB junit testcases
Build
July 5, 2012:
- Milestone Releases
- 2.5.0 M1 (Complete)
- Next: 2.4.1 M1 - today?
- Remove old build pathways
- converting Oracle build to Tycho problematic
- holding in preference to Git migration
- converting Oracle build to Tycho problematic
- Git migration
- working on 'git exersizes' for training
- I'll post new org.eclipse.eclipselink.test.git soon
- have new transactions as of 11776. am in process of importing before "git svn" conversion and posting.
- targeting 3rd week of July (16th) to have local copies of migrated repos for review & use
JPA
- 2.5
- JPA 2.1 jar checked in
MOXy / SDO
2.4 features
2.4.1
- Performance
- Focussing on SpecJ benchmark runs
- Jar footprint reduction
- QA, Testing
- Bug 374765 - EclipseLink 2.3 SDO server test failed on GlassFish
DBWS
2.5 feature planning
- JAX-RS support
- Conversion from native metadata
- Ability to query across D/B schema's
EclipseLink Incubator
EclipseLink/Development/Incubation
- Time to create separate sub-project for incubator
- Increase community of committers
- Try out GIT & eGit/jGit tooling in incubator?
Documentation
Preparing for 2.4 items. Ben put the EL doc plan on the wiki at http://wiki.eclipse.org/EclipseLink/Development/Documentation/2.4
Considering process improvements
JPA Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/JPA
MOXy/JAXB Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/MOXy
DBWS Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/DBWS