[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[pdt-dev] Fwd: [cross-project-issues-dev] Kepler dates

hi,

Friday May, 24th is the deadline to submit IP logs for Kepler, so it's the last chance to commit any patches from contributors for Kepler.
If there's any patch, pull request that you as a contributor or committer know about and would like to push in Kepler time-frame, please ping on bugzilla!

thanks,

Jacek


---------- Forwarded message ----------
From: Wayne Beaton <wayne@xxxxxxxxxxx>
Date: Tue, May 21, 2013 at 7:30 PM
Subject: [cross-project-issues-dev] Kepler dates
To: cross-project-issues-dev@xxxxxxxxxxx


Greetings folks.

Just a friendly reminder that the Kepler dates are coming up.

May 24/2013 - Deadline to submit IP Logs for Kepler releases
June 5/2013 - PMC-approved Review materials submitted to EMO

I've already received a bunch of IP Logs, but nowhere near the 71 that I'm expecting. Please make this happen.

You should also have started your review documentation. Feel free to enter this information into the corresponding release record in the PMI, or use any of the traditional formats.

Please do take a moment to minimally specify a description for your release in your project's release record. A short paragraph with a few sentences describing your release is all I need. I intend to build a page that includes this information as a handy means for somebody to quickly scan the release contents to find things of interest. In this regard a description that states something to the effect of "The project's Kepler release" isn't all that useful.

I've been updating/fixing project descriptions here and there in the PMI. Unfortunately, I am restricted in what I can provide as I am not the best authority regarding what your project does or your release provides. This information is used in a few pages today to drive attention to your project. Making good descriptions will help drive more eyeballs and hopefully solicit additional contribution.

Make sure that you review the release review checklist before you submit your documentation to emo@xxxxxxxxxxx. I've noticed a lot of incorrect "Bundle-Vendor" entries and missing about and license files, for example. Please take the time to get this stuff right.

For PMC approval, all I need is a link to the thread in PMC mailing list that starts with your project's review documentation and ends with at least one +1 from a PMC member.

Please assume that the June 5th deadline is firm. I'm looking at you EGit.

I am tracking each project's Kepler participation and a blocker bug on 406441 [1].

One final note for Modeling projects: per Bug 393682, the Modeling project has been restructured and mid-level "container" projects (e.g. modeling.emf, modeling.emft, etc.) have been marked for termination. Modeling projects that are nested inside a container project will have to be moved into the top level project before your Kepler release can be approved.

As always, let me know if you have any questions.

Wayne

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406441
[2] http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects
EclipseCon
          France 2013

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Title: Kepler dates
Greetings folks.

Just a friendly reminder that the Kepler dates are coming up.

May 24/2013 - Deadline to submit IP Logs for Kepler releases
June 5/2013 - PMC-approved Review materials submitted to EMO

I've already received a bunch of IP Logs, but nowhere near the 71 that I'm expecting. Please make this happen.

You should also have started your review documentation. Feel free to enter this information into the corresponding release record in the PMI, or use any of the traditional formats.

Please do take a moment to minimally specify a description for your release in your project's release record. A short paragraph with a few sentences describing your release is all I need. I intend to build a page that includes this information as a handy means for somebody to quickly scan the release contents to find things of interest. In this regard a description that states something to the effect of "The project's Kepler release" isn't all that useful.

I've been updating/fixing project descriptions here and there in the PMI. Unfortunately, I am restricted in what I can provide as I am not the best authority regarding what your project does or your release provides. This information is used in a few pages today to drive attention to your project. Making good descriptions will help drive more eyeballs and hopefully solicit additional contribution.

Make sure that you review the release review checklist before you submit your documentation to emo@xxxxxxxxxxx. I've noticed a lot of incorrect "Bundle-Vendor" entries and missing about and license files, for example. Please take the time to get this stuff right.

For PMC approval, all I need is a link to the thread in PMC mailing list that starts with your project's review documentation and ends with at least one +1 from a PMC member.

Please assume that the June 5th deadline is firm. I'm looking at you EGit.

Note that I am tracking each project's Kepler participation and a blocker bug on 406441 [1].

As always, let me know if you have any questions.

Wayne

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406441
[2] http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects
EclipseCon
          France 2013