''Welcomed new members, and Stephan and Chuck introduced themselves. Many thank to Kaloyan for his years of service on the Council.''

* Critical IP/review dates announced.

* Critical IP/review dates announced.

Line 152:

Line 155:

: Make sure the projects you represent [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08898.html subscribe to cross-project list].

: Make sure the projects you represent [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg08898.html subscribe to cross-project list].

::If you need a "how to" reminder, see [https://dev.eclipse.org/mailman/listinfo the general Eclipse.org mailing list page] or [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev the specific cross-project page].

::If you need a "how to" reminder, see [https://dev.eclipse.org/mailman/listinfo the general Eclipse.org mailing list page] or [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev the specific cross-project page].

+

+

''Wayne added other reminders, that there will be renewed vigor in making sure projects have project plans, valid websites, operate in an open-transparent way ... and in some cases this means Wayne will involve the PMCs more (who, after all, are responsible for their projects) so ... Planning Council reps, do what you can to remind/monitor the projects you represent.''

+

+

''From Wayne's observations, there are two projects that participate in Sim. Rel., but don't subscribe to cross-project list: DLTK, and Eclipse Runtime Project (both Technology Projects).''

== Kepler ==

== Kepler ==

Line 160:

Line 167:

* Be aware that EGit is moving to "3.0" in M7.

* Be aware that EGit is moving to "3.0" in M7.

+

+

''Build currently broken {{bug|407545}}. Some "compatibility issues" being ironed out. (Forgot to mention during meeting, but Markus communicated with me before the meeting, that EPP builds are "looking better" ... so, maybe I can sleep again :) ''

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.

Wayne added other reminders, that there will be renewed vigor in making sure projects have project plans, valid websites, operate in an open-transparent way ... and in some cases this means Wayne will involve the PMCs more (who, after all, are responsible for their projects) so ... Planning Council reps, do what you can to remind/monitor the projects you represent.

From Wayne's observations, there are two projects that participate in Sim. Rel., but don't subscribe to cross-project list: DLTK, and Eclipse Runtime Project (both Technology Projects).

Kepler

M7 and "end game"

Issues?

Be aware that EGit is moving to "3.0" in M7.

Build currently broken bug 407545. Some "compatibility issues" being ironed out. (Forgot to mention during meeting, but Markus communicated with me before the meeting, that EPP builds are "looking better" ... so, maybe I can sleep again :)

dw create "report of changes" from one build to another, one repo to another, so a) individual projects could see if things changed when they should not have; b) PMCs, Team Leads, Planning council could better observe "big picture" of how much change there was, especially related to changes in build input files.

wayne to add item to release review that "there must be a retention policy" (it should cover how long repos stay around, such as milestone repos, and also via ?education? emphasis that it must be "non-changing".) And then Planning Council can add extra rules for sim. release, if necessary.

Release train rules documentation

John and Neil volunteered to improve. The idea is to provide briefer version, but still (probably via hyperlinks?) allow readers to find out "reasons" for a rule. This would be for Luna (due in Fall, after Kepler release).

Release train rhythm

Wayne volunteered to add suggestion/idea to GSOC database to make some user friendly way that users could say "I want to follow beta releases" ... this would add the "current" development stream URL to update sites, so they'd get updates from milestones, without having to know about it, and manually add it.

Orbit

The Orbit Project Lead (dw) agreed to a plan for a plan ... a plan will be created after Kepler release, by end of August (since July often a "slow" month) ... and implemented in the months after that.

Next Meeting

June 5, 2013 - Regular First Wednesday Meeting - our last before release

July -- No meeting in July - we will be relaxing after release

August 7, 2013 - Regular First Wednesday Meeting ... almost time for SR1!