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"

m (Minutes from Past Meetings)
Line 5: Line 5:
 
'''* 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.'''
 
'''* 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 01 2008 ==
+
== Agenda Oct 08 2008 ==
  
 
[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=13&year=2008&hour=14&min=0&sec=0&p1=188 2PM EST, Wednesday Oct 01, 2008]
 
[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=13&year=2008&hour=14&min=0&sec=0&p1=188 2PM EST, Wednesday Oct 01, 2008]
Line 35: Line 35:
 
*** [http://wiki.eclipse.org/EclipseLink/Development/JPA2.0/derived_ids Derived Ids]
 
*** [http://wiki.eclipse.org/EclipseLink/Development/JPA2.0/derived_ids Derived Ids]
 
**** Started
 
**** Started
 
* Monthly Milestones Starting Aug 13th
 
** Next Milestone - Sept 17th
 
  
 
=== 1.0.2 bugs ===
 
=== 1.0.2 bugs ===
* Peter to add new target.
+
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=RT&product=EclipseLink&target_milestone=1.0.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs]
* small number of bugs - review next week
+
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=RT&product=EclipseLink&target_milestone=1.0.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfield=%5BBug+creation%5D&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= fixed bugs]
  
 
=== General Issues ===
 
=== General Issues ===
* Sept 12, 2008 - Thank you to the SUN GlassFish V3 team for a quick 24h turnaround getting the Eclipse 3.4 GlassFish server plugin updated to 1.0.9 to solve a [http://forums.java.net/jive/thread.jspa?threadID=46901&tstart=0 missing jar problem] as well as helping with a [http://forums.java.net/jive/thread.jspa?threadID=46886&tstart=0 JDK 1.7 conflict during the GF3Prelude install].
+
* SVN Mirrors
 
+
** Discuss
* DONE Bugzilla components - sign-off on final changes below
+
http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00640.html
+
* Automated Testing
+
** Need SRG test models for JPA, MOXy and SDO
+
*** DB components of those tests should be simple enough to run on Derby
+
*** Need to test Core SRG on Derby
+
 
* Build Issues  
 
* Build Issues  
 
** Need to discuss resolution of some issues
 
** Need to discuss resolution of some issues
 
*** Bugs 245394 & 239984 (Milestones should be in version class & Need unique build IDs) proposed changes to Version.class
 
*** Bugs 245394 & 239984 (Milestones should be in version class & Need unique build IDs) proposed changes to Version.class
 
*** Bug 239513: MW not in Continuous Build. Original issue resolved (tests try to run without MW jars built). Question: Do we really want to run MW tests/build in CB? Is build of MW Core classes sufficient to test dependencies?
 
*** Bug 239513: MW not in Continuous Build. Original issue resolved (tests try to run without MW jars built). Question: Do we really want to run MW tests/build in CB? Is build of MW Core classes sufficient to test dependencies?
* Bug Prioritization and targetting
 
** Currently more bugs are scheduled for 1.0.1 then we are likely to fix in that time
 
** We currently do not have a system to ensure a bug has a published priority level
 
** We should discuss how will we deal with these issues
 
* Bug DB usage
 
** If you are working on a bug, assign it to yourself.
 
*** add dummy inbox to the cc list.
 
** Set the target milestone to the correct milestone.
 
*** Confusion/concern on this part
 
*** Milestones
 
**** 1.0M9 are bugs that are to be fixed by the the corresponding milestone build.
 
**** 1.0 is a bug that is to be fixed by 1.0, but has no current target milestone.
 
**** 1.0.1 new bugs should be filed against this target
 
* Bug council
 
** Introduce notion of Bug council
 
** Wed 2:30pm
 
*** Untargeted bugs are going to be reviewed by bug council on a weekly basis (current proposed time is directly after weekly status meeting (2:30 ET on Wednesdays).
 
**** A milestone will be set - or set to future
 
**** Bug may get assigned
 
*** When you enter a new bug, leaving it untargeted means that the bug council will review to decide which release it is targeted for.
 
*** If you know which milestone the bug will be fixed in, assign it accordingly.
 
*** The new target - future - is for bugs that don't have a target yet.
 
* Code headers
 
** Ensure Header is dual license EDL + EPL
 
*** Found and fixed some build xml files.
 
** Ensure contributor is correct - new code should have code author (no - intial code from oracle)
 
*** Found and fixed some build xml files.
 
* WIKI Changes should be done in parallel to any bug fixes to eclipselink.*.test ant targets or other public API changes - mobrien 20080529.
 
 
 
=== Upcoming Issues ===
 
=== Upcoming Issues ===
  

Revision as of 11:56, 8 October 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 Oct 08 2008

2PM EST, Wednesday Oct 01, 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.1M4 11/17/2008 Nov Milestone for 1.1
      • 1.1M5 11/26/2008 RC1 Milestone for 1.1
      • 1.1M6 12/03/2008 RC2 Milestone for 1.1
      • 1.1 12/09/2008 1.1 Released

1.1

1.0.2 bugs

open bugs fixed bugs

General Issues

  • SVN Mirrors
    • Discuss
  • Build Issues
    • Need to discuss resolution of some issues
      • Bugs 245394 & 239984 (Milestones should be in version class & Need unique build IDs) proposed changes to Version.class
      • Bug 239513: MW not in Continuous Build. Original issue resolved (tests try to run without MW jars built). Question: Do we really want to run MW tests/build in CB? Is build of MW Core classes sufficient to test dependencies?

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

Back to the top