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 "Planning Council/August 05 2009"
(→Topics) |
(attendees) |
||
| Line 11: | Line 11: | ||
|}<p></p><p></p><p></p> | |}<p></p><p></p><p></p> | ||
| − | == Attendees == | + | == Attendees == |
{| cellpadding="15" border="0" | {| cellpadding="15" border="0" | ||
| Line 18: | Line 18: | ||
{| border="1" | {| border="1" | ||
|- | |- | ||
| − | |Chris Aniszczyk | + | | Chris Aniszczyk |
| − | |Technology (PMC) | + | | Technology (PMC) |
| − | | | + | | |
|- | |- | ||
| − | |John Arthorne | + | | John Arthorne |
| − | |Eclipse (PMC) | + | | Eclipse (PMC) |
| − | | | + | | Y |
|- | |- | ||
| − | |Wayne Beaton | + | | Wayne Beaton |
| − | |Eclipse Foundation (appointed) | + | | Eclipse Foundation (appointed) |
| + | | | ||
|- | |- | ||
| − | |Cedric Brun | + | | Cedric Brun |
| − | |OBEO (Strategic Developer) | + | | OBEO (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Oliver Cole | + | | Oliver Cole |
| − | |Tptp (PMC) | + | | Tptp (PMC) |
| + | | Y | ||
|- | |- | ||
| − | |Stefan Daume | + | | Stefan Daume |
| − | |Cloudsmith Inc.(Strategic Developer) | + | | Cloudsmith Inc.(Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | | | + | | Brian Payton |
| − | |Datatools (PMC) | + | | Datatools (PMC) |
| + | | Y | ||
|- | |- | ||
| − | |Doug Gaff | + | | Doug Gaff |
| − | |Dsdp (PMC) | + | | Dsdp (PMC) |
| + | | | ||
|- | |- | ||
| − | |Neil Hauge | + | | Neil Hauge |
| − | |Oracle | + | | Oracle (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Mika Hoikkala | + | | Mika Hoikkala |
| − | |Nokia | + | | Nokia (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Anthony Hunter | + | | Anthony Hunter |
| − | |Tools (PMC) | + | | Tools (PMC) |
| + | | | ||
|- | |- | ||
| − | |Oisin Hurley | + | | Oisin Hurley |
| − | |Stp (PMC) | + | | Stp (PMC) |
| + | | | ||
|- | |- | ||
| − | |Markus Knauer | + | | Markus Knauer |
| − | |Innoopract | + | | Innoopract (Strategic Developer) |
| + | | R | ||
|- | |- | ||
| − | |Christian Kurzke | + | | Christian Kurzke |
| − | |Motorola | + | | Motorola (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Ed Merks | + | | Ed Merks |
| − | |Modeling (PMC) | + | | Modeling (PMC) |
| + | | | ||
|- | |- | ||
| − | |Mike Milinkovich | + | | Mike Milinkovich |
| − | |Eclipse Foundation (appointed) | + | | Eclipse Foundation (appointed) |
| + | | | ||
|- | |- | ||
| − | |Kaloyan Raev | + | | Kaloyan Raev |
| − | |SAP AG (Strategic Developer) | + | | SAP AG (Strategic Developer) |
| + | | Y | ||
|- | |- | ||
| − | |James Saliba | + | | James Saliba |
| − | |CA Inc. (Strategic Developer) | + | | CA Inc. (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Sebastian Voigt | + | | Sebastian Voigt |
| − | |brox IT-Solutions GmbH (Strategic Developer) | + | | brox IT-Solutions GmbH (Strategic Developer) |
| + | | | ||
|- | |- | ||
| − | |Thomas Watson | + | | Thomas Watson |
| − | |Rt (PMC) | + | | Rt (PMC) |
| + | | Y | ||
|- | |- | ||
| − | |David Williams | + | | David Williams |
| − | |WTP (PMC) (appointed Chair) | + | | WTP (PMC) (appointed Chair) |
| − | | | + | | Y |
|- | |- | ||
| − | |Gary Xue | + | | Gary Xue |
| − | |Birt (PMC) | + | | Birt (PMC) |
| − | | | + | | |
|} | |} | ||
| − | + | <br><small>Note: feel free to correct any errors/omissions in above attendance record.</small><br><small>Y = attended</small><br><small>R = regrets sent ahead of time</small> | |
| − | <small>Note: feel free to correct any errors/omissions in above attendance record.</small> | + | |
| − | + | ||
| − | <small></small> | + | |
| − | + | ||
| − | <small></small> | + | |
|} | |} | ||
Revision as of 14:27, 5 August 2009
Contents
Logistics
| Meeting Title: | Planning Council Conference Call |
| Date & Time: | Wednesday, August 05, 2009, at 1600 UTC / 0900 SFO / 1200 NYC / 1700 London / 1800 Berlin |
| Dial-in: | For the call-in numbers, see the "Project Review" number on Foundation Portal page. |
Attendees
|
Topics
- Announcements:
- Congratulations and condolences to John Arthorne as new PC rep from Eclipse PMC
- Congratulations and condolences to Oisin Hurley as new EclipseCon program chair!
- Finalize SR1 Plan.
- A concern raised that given +0 is on Monday, and finalized on Friday, that there could be a long period before a regression (discoverd on Thursday or Friday) was fixed.
- For one, there's nothing stopping highly dependent projects or adopters from doing their testing earlier. For example, WTP doesn't have to wait for the Common Discovery Repository delivery before starting their testing.
- For another, exceptions can be worked out on a case-by-case bases, patches supplied, etc., if for example, a regression was so bad it prevented another project or adopter from doing their testsing. (I'd say this is unlikely ... but it does happen).
- Begin Helios Discussions
- similar process of having Common Discover Site
- similar criteria?
- to be in Common Discover Site
- to be in Release
- But with graduated levels of achievement where appropriate (e.g. 5 levels from none to excellent)
- Instead of "pass/fail", require a "statement of intent" for each item as part of Project Plan.
- For example, some projects might declare "no intent to support accessibility checklists".
- Projects would still be excluded on a case by case bases, if felt they interfered with the process, or other projects functionality.
- Hot Items?
- Granularity: sub-Projects vs. Top Level Project?
- capabilities definitions and process?
- others?
- Helios Dates:
- M1 8/7 - 8/21
- M2 9/18 - 10/2
- Initial standard-format plans due 10/2
- M3 10/30 - 11/13
- M4 12/11 - 12/18 [note: beginning of 1 week windows]
- M5 1/29 - 2/5 [seven week span from M4, to account for end-of-year holidays]
- M6 3/12 - 3/19
- EclipseCon 3/22 - 3/25
- M7 4/30 - 5/7 [seven week span from M6, to account for EclipseCon]
- Release: 6/23/2010 (4th Wednesday of June)
- Notes regarding the +0, +1, +2, +3, EPP, and 'available' days
- The first three milestones use a two-week window and the remaining milestones use 1-week windows.
- The sub-deadline patterns within the windows are as follows:
- The first three milestones use a two-week window and the remaining milestones use 1-week windows.
| +0 | +1 | +2 | +3 | EPP | Available | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Friday | Sat | Sun | Mon | Tue | Wed | Thur | Fri | Mon | Tue | Wed | Thur | Fri |
| +0 | +1 | +2 | +3 | EPP | Available |
|---|---|---|---|---|---|
| Friday | Monday | Tuesday | Wednesday | Thursday | Friday |
- Remember, the +n categories represent latest possible time to be complete for what is required of common discovery site (generally, at noon, Eastern time, of the day). Teams have to do their builds and testing before these common-site deadlines.
- In general, teams often have complicated inter-dependencies which are not captured by the simple "+1", "+2" descriptions. In those cases, it is up to those projects to work out their detailed inter-dependencies and processes to satisfy what they need. The dates and deadlines listed by Planning Council, apply only to the final deliverable to the common repository.
- Do we have the right members? What to do about those that are inactive?
- For reference, there are 14 Strategic Members
- Next Meeting
- September 2, Wednesday, Noon Eastern Time.
Reference
Simultaneous_Release_Roles and Simultaneous_Release_Roles/EMO