Jump to: navigation, search

Difference between revisions of "Planning Council/September 05 2012"

(Continue and conclude annual debrief)
(Begin Kepler Requirements Planning)
 
(7 intermediate revisions by the same user not shown)
Line 42: Line 42:
 
| John Arthorne
 
| John Arthorne
 
| Eclipse (PMC)  
 
| Eclipse (PMC)  
|
+
| Y
 
|-
 
|-
 
| Steffen Pingel  
 
| Steffen Pingel  
 
| Mylyn (ALM) PMC  
 
| Mylyn (ALM) PMC  
|
+
| Y
 
|-
 
|-
 
| Brian Payton  
 
| Brian Payton  
 
| Datatools (PMC)  
 
| Datatools (PMC)  
|
+
| Y
 
|-
 
|-
 
| Doug Schaefer
 
| Doug Schaefer
Line 66: Line 66:
 
| Ian Bull (Plus Jesse, transition)
 
| Ian Bull (Plus Jesse, transition)
 
| Rt (PMC)  
 
| Rt (PMC)  
|
+
| Y
 
|-
 
|-
 
| David Williams  
 
| David Williams  
 
| WTP (PMC) (appointed Chair)  
 
| WTP (PMC) (appointed Chair)  
|
+
| Y
 
|-
 
|-
 
| Gary Xue  
 
| Gary Xue  
Line 78: Line 78:
 
| Wayne Beaton  
 
| Wayne Beaton  
 
| Eclipse Foundation (appointed)  
 
| Eclipse Foundation (appointed)  
|
+
| Y
 
|}
 
|}
 
|
 
|
Line 90: Line 90:
 
| Neil Hauge  
 
| Neil Hauge  
 
| Oracle (Strategic Developer)  
 
| Oracle (Strategic Developer)  
|  
+
|
 
|-
 
|-
 
| Kaloyan Raev  
 
| Kaloyan Raev  
Line 102: Line 102:
 
| Markus Knauer  
 
| Markus Knauer  
 
| Innoopract (Strategic Developer)  
 
| Innoopract (Strategic Developer)  
|
+
| Y
 
|-
 
|-
 
| Achim Loerke  
 
| Achim Loerke  
 
| BREDEX (Strategic Developer)  
 
| BREDEX (Strategic Developer)  
|
+
| Y
 
|-
 
|-
 
| (PMC rep)
 
| (PMC rep)
Line 134: Line 134:
  
 
* ?
 
* ?
 +
 +
: ''none''
  
 
== Juno SR1 ==
 
== Juno SR1 ==
  
 
* SR1 coming soon! See [[Juno/Simultaneous_Release_Plan#Service_Releases]]. Issues? Problems?
 
* SR1 coming soon! See [[Juno/Simultaneous_Release_Plan#Service_Releases]]. Issues? Problems?
 +
 +
: ''One issue was mentioned at end of meeting, where Tycho? signing plugin? (something) changed that broke ability to sign and produce packed jars. [Apologies, not sure who was speaking]. But they said they'd have to research more to figure out what the issue what (they'd just returned from vacation) ... if issue was that "builder suddenly changed on them" (and they don't know how to specify a particular one) or if "no one is responsible for overall framework" (or, something like that, I'm sure I'm misquoting). If this is about {{bug|387557}} then yes, jar processor should be fixed, but seems like possibly could be worked around? But, member said they'd have to look into it more and get back to us once they'd "caught up" from being out.''
  
 
== Kepler ==
 
== Kepler ==
Line 151: Line 155:
 
: Feel free to add things to the page before the meeting, if that would facilitate discussion.  
 
: Feel free to add things to the page before the meeting, if that would facilitate discussion.  
  
: ''Some good points raised. We will re-visit in September.''  
+
: ''Mostly discussed "runtime projects" as has been being discussed on Rt PMC list. I noted a few things in [[Planning_Council/Juno_retrospective]] but was thought to be an on-going discussion.''  
  
 
: Be sure to read last years: [[Planning_Council/Indigo_retrospective]]
 
: Be sure to read last years: [[Planning_Council/Indigo_retrospective]]
  
== Begin Kepler Requirements Planning ==  
+
=== Begin Kepler Requirements Planning ===  
  
 
* [[SimRel/Simultaneous_Release_Requirements]]
 
* [[SimRel/Simultaneous_Release_Requirements]]
  
 
: Begin discussion of requirements, if changes needed. To the extent possible, I suggest we start with high level issues this month (such as, should any be added, removed?) and perhaps finish up with wording changes for clarification (if any) next month.
 
: Begin discussion of requirements, if changes needed. To the extent possible, I suggest we start with high level issues this month (such as, should any be added, removed?) and perhaps finish up with wording changes for clarification (if any) next month.
 +
 +
:''Didn't discuss much. I brought up issue of low compliance to "greediness" issue, and as far as I know, to define everything in features is the only way for adopters to provide patches ... so ... either I need education, or better educate others on why important? Or ... maybe others don't need patches? What's alternative? New release? (which, adopters can not do "on their own", typically, such as for a "hot fix" for one customer). ''
  
 
== Other Business ==
 
== Other Business ==
  
 
* What's status of new "Portal Interface"? (Wayne?). Is it (nearly) ready to use for "Simultaneous Release data"? For example, links to ramp down plan, accessibility support, reports? Etc.
 
* What's status of new "Portal Interface"? (Wayne?). Is it (nearly) ready to use for "Simultaneous Release data"? For example, links to ramp down plan, accessibility support, reports? Etc.
 +
 +
: ''Wayne said "release 1" is tentatively expected end of this month. This would replace most (basic) functionality of current portal ... enhancements would be added from there. To add "Simultaneous Release tracking" (e.g. URLs for rampdown plans, accessibility, etc.), would be considered, but "low on the list". Mostly focused on integrating plans/releases so they are all easier, whether yearly train or not, if I understood sentiment.''
 +
  
 
* {{bug|365738}} Procedure and trade-offs for explicit "sign up" for "the next" Simultaneous Release.
 
* {{bug|365738}} Procedure and trade-offs for explicit "sign up" for "the next" Simultaneous Release.
 +
 +
: ''No one seemed to think it that hard the way it was, and was useful to show "people still involved". Granted, more could be done with automation, but seemed lower on priority than other things. Concluded with asking PC members to comment on {{bug|365738}} if they had opinions or improvements.''
  
 
== Next Meeting  ==
 
== Next Meeting  ==

Latest revision as of 14:43, 5 September 2012

Logistics

Meeting Title: Planning Council Conference Call
Date & Time: Wednesday, August 01, 2012, at 1200 Eastern
Dial in: (See Asterisk service for complete details on SIP, potential new numbers, phone mute commands, etc.)

Phone Numbers:

  • Ottawa (local call in Ottawa) 1-613-454-1403
  • North America (toll free) 1-877-369-7806
  • Germany (local call anywhere in Germany) +49-692-2224-6059
  • France (local call anywhere in France) +33-17-070-8535
  • UK (toll free) 0800-033-7806
  • Switzerland (local call anywhere in Switzerland) +41-44-580-2115
Participant conference extension: 710 then enter pin 35498
  • SIP clients:
call 710@asterisk.eclipse.org, then enter pin 35498.

Members and Attendees

PMC (and Strategic) Reps
Chris Aniszczyk Technology (PMC)
John Arthorne Eclipse (PMC) Y
Steffen Pingel Mylyn (ALM) PMC Y
Brian Payton Datatools (PMC) Y
Doug Schaefer Tools (PMC)
Adrian Mos SOA (PMC)
Ed Merks Modeling (PMC)
Ian Bull (Plus Jesse, transition) Rt (PMC) Y
David Williams WTP (PMC) (appointed Chair) Y
Gary Xue Birt (PMC)
Wayne Beaton Eclipse Foundation (appointed) Y
Strategic Reps
Cedric Brun OBEO (Strategic Developer)
Neil Hauge Oracle (Strategic Developer) Y
Kaloyan Raev SAP AG (Strategic Developer)
Igor Fedorenko Sonatype (Strategic Developer)
Markus Knauer Innoopract (Strategic Developer) Y
Achim Loerke BREDEX (Strategic Developer) Y
(PMC rep) Actuate (Strategic Developer) X
(PMC rep) IBM (Strategic Developer) X
Inactive
[no name] CA Inc. (Strategic Consumer) X

Note: "Inactive" refers to Strategic Members or PMCs we have not heard from for a while, and have been unable to convince to participate. Those members can become active again at any time. Contact David Williams if questions.

Note: feel free to correct any errors/omissions in above attendance record.
Y = Yes, attended
N = No, did not
R = regrets sent ahead of time
D = delegated
X = not expected

Announcements

  •  ?
none

Juno SR1

One issue was mentioned at end of meeting, where Tycho? signing plugin? (something) changed that broke ability to sign and produce packed jars. [Apologies, not sure who was speaking]. But they said they'd have to research more to figure out what the issue what (they'd just returned from vacation) ... if issue was that "builder suddenly changed on them" (and they don't know how to specify a particular one) or if "no one is responsible for overall framework" (or, something like that, I'm sure I'm misquoting). If this is about bug 387557 then yes, jar processor should be fixed, but seems like possibly could be worked around? But, member said they'd have to look into it more and get back to us once they'd "caught up" from being out.

Kepler

Continue and conclude annual debrief

Feel free to add things to the page before the meeting, if that would facilitate discussion.
Mostly discussed "runtime projects" as has been being discussed on Rt PMC list. I noted a few things in Planning_Council/Juno_retrospective but was thought to be an on-going discussion.
Be sure to read last years: Planning_Council/Indigo_retrospective

Begin Kepler Requirements Planning

Begin discussion of requirements, if changes needed. To the extent possible, I suggest we start with high level issues this month (such as, should any be added, removed?) and perhaps finish up with wording changes for clarification (if any) next month.
Didn't discuss much. I brought up issue of low compliance to "greediness" issue, and as far as I know, to define everything in features is the only way for adopters to provide patches ... so ... either I need education, or better educate others on why important? Or ... maybe others don't need patches? What's alternative? New release? (which, adopters can not do "on their own", typically, such as for a "hot fix" for one customer).

Other Business

  • What's status of new "Portal Interface"? (Wayne?). Is it (nearly) ready to use for "Simultaneous Release data"? For example, links to ramp down plan, accessibility support, reports? Etc.
Wayne said "release 1" is tentatively expected end of this month. This would replace most (basic) functionality of current portal ... enhancements would be added from there. To add "Simultaneous Release tracking" (e.g. URLs for rampdown plans, accessibility, etc.), would be considered, but "low on the list". Mostly focused on integrating plans/releases so they are all easier, whether yearly train or not, if I understood sentiment.


  • bug 365738 Procedure and trade-offs for explicit "sign up" for "the next" Simultaneous Release.
No one seemed to think it that hard the way it was, and was useful to show "people still involved". Granted, more could be done with automation, but seemed lower on priority than other things. Concluded with asking PC members to comment on bug 365738 if they had opinions or improvements.

Next Meeting

  • October 3, 2012 (our regular "first Wednesday" meeting, at Noon Eastern).
Plan for Kepler

Reference

Kepler Wiki page
Juno Wiki page
Planning Council/Indigo retrospective
Planning Council Members
Simultaneous Release Roles and Simultaneous Release Roles/EMO