| [eclipselink-dev] Minutes: EclipseLink Dev Meeting Nov. 29 |
Attendees Kyle Chen, Gordon Yorke, Guy Pelletier, Tom Ware, Rick Sapir, Michael O'Brien, David Twelves, Mike Norman, Doug Clarke, Roger Striffler, Shaun Smith, Peter Krogh Status updates 1.0M2 * Automated build. Logs from last 2 weeks available on Wiki * Automated testing. Running against mySQL. Foundation tests not running to completion - permissions issue? * JavaDocs. Javadoc zip to be packaged inside incubation zip. Expanded view to be refreshed for each milestone. Need stats on how many people are downloading nightly builds (will be available shortly). * Deprecation removal. Kyle to send out transaction for review. Goal is to have no deprecated code in 1.0 release. * SDO2.1 functionally complete - on target for Dec 7th, may just miss Dec 5 M2 milestone. * Doc status. Conversion to Wiki format ongoing. User Guide has been split into set of categories to aid searching. * 1.0M2. Action item: Committers to check target milestone set correctly in bug database. 1.0M3 * 1.0M3. Action item: Committers to review targets for M3 and propose any other major goals. 1.0 Exit Criteria * Exit criteria being established. Completion of this list and work estimates will drive projected release date. General issues * JOTM. Action item: Gordon to come up with proposal whether it makes sense to use JOTM in our testing infrastructure. Does a Spring test environment cover all our server test needs? * Committer check-in process. Action item: All committers to ensure all components are compiled at a minimum when submitting a transaction. Can use ant script for this if all components not available in Eclipse project. Action item: Peter to investigate continuous build (Dali already has one). New mailing list for notifications required. Can new transaction info be included in email? * Build artifacts installer.zip should be removed from repository. eclipselink.jar. Should generate this on a nightly basis, but will need to be checked into a different place to avoid refresh issue. * Component name changes in bugzilla approved (as listed in agenda). Documentation bugs should be flagged in Keyword field. * Equinox. Shaun has successfully been testing this. Some packaging issues remain. Bug opened to track this as a development activity. Progress will be captured on Wiki page. * Tagging. Mechanism available to tag chosen builds as required. Tagging strategy needs to be captured on Wiki. * Dev process: emails Concern that submission notification emails are overloading dev mailing list. Proposal: rely on bug database updates to provide notifications. Concern is that code review notifications may be lost. -> No resolution to this issue. Continue using dev mailing list for now. Action item: Everyone should register for notifications via dummy emails if desired (see agenda for instructions) * Testing infrastructure proposal. Discussion ongoing. Concern about number of contexts that would be required by current proposal. Concern that JUnit3 is end-of-life, but an alternate JUnit4 runner would be required to provide backwards compatibility with existing TopLink test framework. Action item: Interested parties to review proposal before next meeting.
<<attachment: winmail.dat>>