Skip to main content

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

Difference between revisions of "EclipseLink/Development/DevMeetings"

(1.0M3)
Line 44: Line 44:
 
** Adding crosslinks from/to examples, FAQs, etc.
 
** Adding crosslinks from/to examples, FAQs, etc.
 
** Working on [[EclipseLink/UserGuide/Contributor_Guidelines|Contributor Guidelines]]
 
** Working on [[EclipseLink/UserGuide/Contributor_Guidelines|Contributor Guidelines]]
 +
* OSGi/Equinox and EclipseLink
 +
** Proposal to create branch in SVN for exploration of [[EclipseLink/Development/OSGi|EclipseLink as OSGi bundles]].
  
 
==== 1.0 Exit Criteria ====
 
==== 1.0 Exit Criteria ====

Revision as of 17:58, 8 January 2008


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.

Agenda Jan 9, 2008

2PM EST, Wednesday January 9th, 2008

Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546

Status updates

  • IP Review (EclipseLink/IPLog)
    • EclipseLink/Dependencies - All approved. Still need PMC approval for 3rd party dependencies - Doug
    • Main TopLink Contribution awaiting final review
    • Workbench CQ Approved
    • UserGuide CQ Approved
  • Dual Licensing with BSD
    • Awaiting BSD availability. Working with Eclipse Foundation legal
    • Will update all source in SVN and CQ with dual license header when available

1.0M3

  • Proposed delivery date: January 8th, 2008
  • Automated build
    • Continuous builds - Action item: Peter to investigate continuous build
      • Simple continuous build up and running (V1.0)
        • compiling only (No automated tests running)
        • email sent to dev list if the build fails. info sent in the email.
        • Build kicked off every half hour on the half hour between 6:00am and 8:00pm. No change detection
  • Automated Testing
    • Some refactoring of the build scripts has occurred to allow tests to run more smoothly. More is coming.
    • JPA FullRegressionTestSuite and core SRG pass on EclipseLink build server
    • JPA, MOXy, SDO and DBWS SRGs are needed
    • Core SRG runs automatically with build
    • Publication of test results
      • HTML version of Core SRG results published with each build
  • Foundation and JPA Status - Peter K
    • Deprecation Removal - Kyle
  • OXM, JAXB, SDO - Blaise D
  • Documentation Status - Rick S
  • OSGi/Equinox and EclipseLink

1.0 Exit Criteria

  • 1.0 Exit Criteria now documented. Please review and provide feedback on the dev mailing list - Doug
  • Need to provide projected release date. Planning for first half of 2008. Waiting for JAXB 2.1 compliance estimates - Doug

General Issues

  • nightly eclipselink.jar checked into build -
  • new Productname EPS(EclipseLink) may be causing issues with our meta data
    • Bugs button is now greyed out, and I can't figure out how to fix it. Escape brackets???
  • Auto generation of backlog list from bugs.
    • Like to try this for M3. Peter to follow up
  • SVN Proxy

Upcoming Issues

The following items require discussion but are not yet at the stage where a solution can be proposed.

Minutes from Past Meetings

Back to the top