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.

Jump to: navigation, search

Revision as of 10:56, 26 July 2012 by Eric.gwin.oracle.com (Talk | contribs) (→‎Build)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

11 am EST, Thurs

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
- http://wiki.eclipse.org/EclipseLink/Development/Process/Git
Status
- eclipse.runtime live.
  - Need to review development strategy
  - Need to file bug to reduce test package names (Moxy)
    - Means standards aregarding max package length
- Need to publish javax.persistence, finish Hermes, buildsystem, and discuss utils strategy.

QA

July 12-19, 2012:

EclipseLink Nightly Results (Updated on 2012-07-19)
- trunk - 1 new failure with jpars - investigating; one new failure with DBWS example testing on all appliation servers - developer is investigating; most jpa-lrg failed on JRockit16 - bug: 384842. (the last build is 2012-07-16)
- 2.4.1 - 1 new failure with jpars - same as trunk (the last build is 2012-07-14)
- 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-13)
Testing
- JPA-RS testing EL 2.4 against WLS 12.1.1 - in progress
Test Dev
- Metadata caching feature completed -- reviewed feature with dev
Test infrastructure
- Test Infra migration to Git - complete; some refactoring work required
- 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
This week:
- Git Migration testing
- 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 26, 2012:

Milestone Releases
- None (on hold)
- Next: 2.4.1 M!, 2.5.0 M2
Remove old build pathways
- converting Oracle build to Tycho problematic
  - holding in preference to Git migration
Git Build migration
- Migrated to Hudson for nightly builds
  - Builds and tests running.
  - publishing problematic
    - Archive publish to download fairly straightforward
    - Maven generation has all pieces needed, but needs access to Maven generation script
      - Good reason to split buildsystem away (but will use local git clone in the meantime
    - P2 a problem. needs branch specific info for generation.
      - Need to create p2 archive with build, and then change publish process to publish it.
    - Milestone promotion dependent upon resolving above.