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

EclipseLink/Development/DevMeetings


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 Oct 15 2008

2PM EST, Wednesday Oct 15, 2008

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

Status updates

  • Roadmap in a new plan format
    • upcoming dates
      • 1.1M3 10/17/2008 Oct Milestone for 1.1
      • 1.0.2M1 10/15/2008 M1 Milestone for 1.0.2
      • 1.0.2M2 10/22/2008 RC Milestone for 1.0.2
      • 1.0.2 10/29/2008 1.0.2 Released
      • 1.1.0M4 11/17/2008 Nov Milestone for 1.1.0
      • 1.1.0M5 11/26/2008 RC1 Milestone for 1.1.0
      • 1.1.0M6 12/03/2008 RC2 Milestone for 1.1.0
      • 1.1.0 12/09/2008 1.1.0 Released

1.1.0

1.0.2 bugs

open bugs

fixed bugs

General Issues

  • SVN Mirrors
    • Discuss
    • Need migration of our repository to 1.5 to proceed (No ETA yet).
  • Build Issues
    • Status:
      • Bugs 245394 & 239984 proposed changes to Version.class and change to three digit versions. Will be committing today or tomorrow.
      • Bug 239513: Will modify build to include full mw build and test after have committed above. if it fits within a half hour, we will keep change.
    • Discussion:
      • Can we please remove checked in Derived Objects (built files) from our process? Examples are OK. They are not part of regular build.
        • Causing merge conflicts on build machine (ok now, but may not be later)
        • Revision of built object is NOT guaranteed to contain the source that built it.
        • Causes conflicted updates locally (must rename or delete files to proceed correctly).
        • Once we have revision number linked to the build files, there is little need. periodic backups of all milestones would accomplish stated goal without the side-effects.
  • Bug DB usage
    • Ensuring all Foundation/Core bugs get an initial triage on at least a weekly basis. After review, target version and some other fields will be set. This represents an initial plan. Anyone who disagrees with the changes should either raise the issue by email or at this meeting.
      • As part of the review, now making better use of Priority field. P1 means emergency and work should be done immediately. P2 + non-null target means this bug is a should be considered a requirement for the targetted release
      • Also using two values in Status Whiteboard
        • "patch" means there is a user submitted patch. The goal is to encourage contribution by attempting to integrate bugs with user submitted patches more quickly. We will start by working through the backlog.
        • "trivial" indicates that the fix itself is trivial. Should be used for issues like typos and other issues where a successful compile is adequate to confirm the fix.
      • Bugs listed with severity = enhancement will be reviewed at a later time in conjunction with release planning

Upcoming Issues

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

Minutes from Past Meetings

References

Retrieved from "https://wiki.eclipse.org/index.php?title=EclipseLink/Development/DevMeetings&oldid=123569"

Back to the top