:Feb 8/2013 - CQ deadline for Kepler; CQs for participating projects received by this date will be placed in the IP team's priority queue.

+

:May 24/2013 - Deadline to submit IP Logs for Kepler releases

+

:June 12/2013 - Kepler Uber Release review

+

:June 26/2013 - Kepler release

== Juno ==

== Juno ==

−

* SR2 coming up.

+

* SR2 coming up.

+

+

:* Issues?

+

+

: EGit planning 2.3, but 2.1 is still their common repo contribution? (That is, why aren't they "fully participating"?) See {{bug|399437}}. Kepler contribution is even further behind.

+

+

: '''Action Item:''' Chris will "get back to us" on what EGit's plans are ... he initially thought "final code" would be done in two weeks, but I reminded him RC4/final builds are next Wednesday.

== Kepler ==

== Kepler ==

* It is almost M5! Everyone in?

* It is almost M5! Everyone in?

−

:: Exceptions to M4 deadline: XWT (Kepler M5)

+

:: Exceptions to M4 deadline: XWT, m2e-wtp (Kepler M6)

+

:: '''Action Items:''' Chris, and Wayne, respectively, will send out more detailed proposal/justification for these to "come in late" during M6. There were questions on if they would be "Incubating" or not (currently are, but might be ready for a "graduation review").

* ''Wayne briefed us on status of "PMI" (?Project Management Information?) and said he's about to blog and "send instructions" for new system, but soon, metadata will be accessed for editing, by committers, from their own project page. ''

+

: ''He had question/proposal about projects "adding themselves to release train" ... first, technically, only he could do it now ("tracker" removed from Portal), but he was thinking it'd be good to change the process a little where each project would had to request it (say, on cross project list?), and then be added by him, or Planning Council member. This improves communication, but also prevent "accidental" abuse of projects just adding themselves at any time ... such as under old system, someone could add their project during RC3 if they misunderstood the process (or, even, a previous release!).''

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.

Announcements

Feb 8/2013 - CQ deadline for Kepler; CQs for participating projects received by this date will be placed in the IP team's priority queue.

May 24/2013 - Deadline to submit IP Logs for Kepler releases

June 12/2013 - Kepler Uber Release review

June 26/2013 - Kepler release

Juno

SR2 coming up.

Issues?

EGit planning 2.3, but 2.1 is still their common repo contribution? (That is, why aren't they "fully participating"?) See bug 399437. Kepler contribution is even further behind.

Action Item: Chris will "get back to us" on what EGit's plans are ... he initially thought "final code" would be done in two weeks, but I reminded him RC4/final builds are next Wednesday.

Kepler

It is almost M5! Everyone in?

Exceptions to M4 deadline: XWT, m2e-wtp (Kepler M6)

Action Items: Chris, and Wayne, respectively, will send out more detailed proposal/justification for these to "come in late" during M6. There were questions on if they would be "Incubating" or not (currently are, but might be ready for a "graduation review").

Approved exceptions:

Stardust for M5 approved on mailing list.

Other Business

Wayne briefed us on status of "PMI" (?Project Management Information?) and said he's about to blog and "send instructions" for new system, but soon, metadata will be accessed for editing, by committers, from their own project page.

He had question/proposal about projects "adding themselves to release train" ... first, technically, only he could do it now ("tracker" removed from Portal), but he was thinking it'd be good to change the process a little where each project would had to request it (say, on cross project list?), and then be added by him, or Planning Council member. This improves communication, but also prevent "accidental" abuse of projects just adding themselves at any time ... such as under old system, someone could add their project during RC3 if they misunderstood the process (or, even, a previous release!).