Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/DevMeetings/20080917"
m (New page: =EclipseLink Development Meeting 20080917= Minutes are preceeded by > 17 Sept 2008 Minutes --------------------- Attendees: Krogh Peter; Twelves David; Doughan Blaise; O'Brien Michael...) |
m (→EclipseLink Development Meeting 20080917) |
||
Line 19: | Line 19: | ||
--------------------- | --------------------- | ||
>Action: Peter: propose cancel the meeting next week | >Action: Peter: propose cancel the meeting next week | ||
+ | |||
>Action: Peter: confirm with Doug on date/content for 1.0.2 release | >Action: Peter: confirm with Doug on date/content for 1.0.2 release | ||
>javadocs for m2 up today | >javadocs for m2 up today | ||
+ | |||
>Most callers at open world next week | >Most callers at open world next week | ||
+ | |||
>Action: Peter: propose cancel the meeting next week | >Action: Peter: propose cancel the meeting next week | ||
+ | |||
>Mitesh would like to review all the glassfish bugs for input into eclipselink | >Mitesh would like to review all the glassfish bugs for input into eclipselink | ||
+ | |||
>A: considering ~2 for EclipseLink | >A: considering ~2 for EclipseLink | ||
+ | |||
>Q: will there be a 1.0.2 | >Q: will there be a 1.0.2 | ||
+ | |||
>A: there are a couple bugs in the 1.0 stream - not in the 1.0.1 stream | >A: there are a couple bugs in the 1.0 stream - not in the 1.0.1 stream | ||
+ | |||
>Threading and test case issues potential candidates for 1.0.2 | >Threading and test case issues potential candidates for 1.0.2 | ||
+ | |||
>End of Oct 2008 potential for 1.0.2 - limited to ~10 showstopper bugs - to stabilize the release | >End of Oct 2008 potential for 1.0.2 - limited to ~10 showstopper bugs - to stabilize the release | ||
Line 36: | Line 45: | ||
>Q: Examples placement | >Q: Examples placement | ||
+ | |||
We need to work out the automated build/testing strategy for these ongoing examples. | We need to work out the automated build/testing strategy for these ongoing examples. | ||
+ | |||
1) SVN - linkable from a wiki | 1) SVN - linkable from a wiki | ||
+ | |||
2) SVN + zip of example (that is linkable from a wiki) | 2) SVN + zip of example (that is linkable from a wiki) | ||
+ | |||
>developers without an SVN account - can use the SVN weblink | >developers without an SVN account - can use the SVN weblink | ||
+ | |||
3) in download directory possibly as a single zip file | 3) in download directory possibly as a single zip file | ||
+ | |||
>We need to be carefull with derived files like eclipselink.* at the root | >We need to be carefull with derived files like eclipselink.* at the root | ||
+ | |||
+ | |||
4) Tom: use a separate zip directory that is not used for building source | 4) Tom: use a separate zip directory that is not used for building source | ||
>example: check in example source for 1.0.1 but only the zip for 1.0 | >example: check in example source for 1.0.1 but only the zip for 1.0 | ||
+ | |||
>essentially examples for 1.0.2 | >essentially examples for 1.0.2 |
Latest revision as of 14:29, 17 September 2008
EclipseLink Development Meeting 20080917
Minutes are preceeded by >
17 Sept 2008 Minutes
Attendees:
Krogh Peter; Twelves David; Doughan Blaise; O'Brien Michael; Ware Tom; Meswani Mitesh; Smith Shaun; Sapir Rick; Hauge Neil; Barkhouse Rick;
Actions:
>Action: Peter: propose cancel the meeting next week
>Action: Peter: confirm with Doug on date/content for 1.0.2 release
>javadocs for m2 up today
>Most callers at open world next week
>Action: Peter: propose cancel the meeting next week
>Mitesh would like to review all the glassfish bugs for input into eclipselink
>A: considering ~2 for EclipseLink
>Q: will there be a 1.0.2
>A: there are a couple bugs in the 1.0 stream - not in the 1.0.1 stream
>Threading and test case issues potential candidates for 1.0.2
>End of Oct 2008 potential for 1.0.2 - limited to ~10 showstopper bugs - to stabilize the release
>1.1 aligning with soft code freeze on glassfish
>Q: Examples placement
We need to work out the automated build/testing strategy for these ongoing examples.
1) SVN - linkable from a wiki
2) SVN + zip of example (that is linkable from a wiki)
>developers without an SVN account - can use the SVN weblink
3) in download directory possibly as a single zip file
>We need to be carefull with derived files like eclipselink.* at the root
4) Tom: use a separate zip directory that is not used for building source
>example: check in example source for 1.0.1 but only the zip for 1.0
>essentially examples for 1.0.2