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.
Difference between revisions of "Planning Council/February 01 2012"
(→Issues or Exceptions) |
(→Members and Attendees) |
||
Line 23: | Line 23: | ||
| Chris Aniszczyk | | Chris Aniszczyk | ||
| Technology (PMC) | | Technology (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| John Arthorne | | John Arthorne | ||
| Eclipse (PMC) | | Eclipse (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Mik Kersten | | Mik Kersten | ||
Line 35: | Line 35: | ||
| Brian Payton | | Brian Payton | ||
| Datatools (PMC) | | Datatools (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Doug Schaefer | | Doug Schaefer | ||
Line 41: | Line 41: | ||
| | | | ||
|- | |- | ||
− | | Adrian Mos ( | + | | Adrian Mos (R.... ?) |
| SOA (PMC) | | SOA (PMC) | ||
− | | | + | | D |
|- | |- | ||
| Ed Merks | | Ed Merks | ||
Line 51: | Line 51: | ||
| Jesse McConnell | | Jesse McConnell | ||
| Rt (PMC) | | Rt (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| David Williams | | David Williams | ||
| WTP (PMC) (appointed Chair) | | WTP (PMC) (appointed Chair) | ||
− | | | + | | Y |
|- | |- | ||
| Gary Xue | | Gary Xue | ||
Line 79: | Line 79: | ||
| Neil Hauge | | Neil Hauge | ||
| Oracle (Strategic Developer) | | Oracle (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| Kaloyan Raev | | Kaloyan Raev | ||
Line 87: | Line 87: | ||
| Pascal Rapicault | | Pascal Rapicault | ||
| Sonatype (Strategic Developer) | | Sonatype (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| Markus Knauer | | Markus Knauer | ||
| Innoopract (Strategic Developer) | | Innoopract (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| Christian Kurzke | | Christian Kurzke | ||
Line 99: | Line 99: | ||
| Achim Loerke | | Achim Loerke | ||
| BREDEX (Strategic Developer) | | BREDEX (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| (PMC rep) | | (PMC rep) |
Revision as of 14:09, 1 February 2012
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, February 01, 2012, at 1200 Eastern |
Dial-in: | For the call-in numbers, see the "Project Review" number on Foundation Portal page. |
Members and Attendees
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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
- Any?
Indigo SR2
- Any issues?
Juno
Issues or Exceptions
- Any issues? Everyone in? Any exceptions known?
- Exceptions for projects not in M4, that still will to join Juno:
- Virgo approved during 1/05 meeting (from rt PMC list, will be in M6)
- BPEL approved on mailing list (as late for M4, but in M5)
-
... code recommenders (in by M5, but not in M4?) Did anyone bring them forward for exception?- Issue Resolved (good to know some people read agenda :) ... but, is process unclear? ... Chris? :)
- Code Recommenders approved on mailing list (as late for M4, but in M5).
- Others?
- Anyone "dropping out" that should be removed from aggregation build?
- I know there are potential, possible issues with Riena (not being in common repo, as _might_ not "achieve 4.2". Discussions on-going.
- Anyone else? How to compare "participating projects" list with "b3aggrcon" files?
Plans
- anything to look at? In particular, plans specifying "planned support for 3.8 workbench"?
Juno+1 Name
- Kepler (EMO has vetted the name ... thanks Chris!)
- Guess I should announce? Or do you want to Chris? On committers list?
Other Business
- Need discussion and decision on "what is allowed in common info center". Pros? Cons? Alternatives? See bug 369395.
- Thoughts on "Java Development Tools" category? See bug 369258 [Immediate issue has been resolved, but, not many comments ... so, feel free to comment or open new bugs on "categories"].
- Fair (and desired?) to add "provide non-greedy repository" to requirements? 'Should' or 'must'? See Provide_optimized_p2_repository section. I propose:
Clarification on 01/23/2012: the repositories produced and contributed (for Juno and subsequent releases) must use p2 publishers that use greedy='false' by default. See bug 247099 and the p2 Publisher wiki for some history and details on this issue of greedy vs. non-greedy requirements.
- Project Priorities: Please review and be prepared to discuss this proposed "policy document" about project priorities.
- Still comfortable with "4.2 as primary"?
- Anything else?
Next Meeting
- March 7, 2012 (our regular "first Wednesday" meeting, at Noon Eastern).