pdt-dev http://dev.eclipse.org/mhonarc/lists/pdt-dev/maillist.html pdt-dev en-us Thu, 23 May 2013 10:40:09 GMT Thu, 23 May 2013 10:40:09 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) pdt-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/pdt-dev/maillist.html [pdt-dev] [Hudson] Hudson build is back to stable : pdt-master #80 http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02439.html See &lt;https://hudson.eclipse.org/hudson/job/pdt-master/80/changes&gt; -- This message is automatically generated by Hudson. For more information on Hudson, see: http://hudson-ci.org/ See <https://hudson.eclipse.org/hudson/job/pdt-master/80/changes> -- This message is automatically generated by Hudson. For more information on Hudson, see: http://hudson-ci.org/ ]]> Thu, 23 May 2013 10:30:59 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02439.html hudsonbuild@xxxxxxx (hudsonbuild) [pdt-dev] Fwd: [cross-project-issues-dev] Kepler dates http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02438.html hi,Friday May, 24th is the deadline to submit IP logs for Kepler, so it&#39;s the last chance to commit any patches from contributors for Kepler.If there&#39;s any patch, pull request that you as a contributor or committer know about and would like to push in Kepl... 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
]]> Wed, 22 May 2013 20:03:30 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02438.html jacek.pospychala@xxxxxxx (Jacek Pospychała) [pdt-dev] Commit rights notifications http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02437.html hi, you might have noticed some notifications about removing commit rights. It's not that PDT team has just committed suicide or something like that. :-) It's only a formal status update to reflect that PDT is currently actively maintained by 3 people (Zha... hi, you might have noticed some notifications about removing commit rights. It's not that PDT team has just committed suicide or something like that. :-) It's only a formal status update to reflect that PDT is currently actively maintained by 3 people (Zhao, Natalia and me). All the other ones have been involved in project as committers in the past, but were no longer active for at least a year. Jacek ]]> Wed, 22 May 2013 19:55:08 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02437.html jacek.pospychala@xxxxxxx (Jacek Pospychała) [pdt-dev] Commit rights for Roy Ganor have been expired http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02436.html tools.pdt Committers, Jacek Pospychala has expired the commit rights for Roy Ganor (rganor). The reason for this change is: Removing commit rights for Roy who hasn't been actively developing PDT for last year. Thank you for all your contributions Roy! tools.pdt Committers, Jacek Pospychala has expired the commit rights for Roy Ganor (rganor). The reason for this change is: Removing commit rights for Roy who hasn't been actively developing PDT for last year. Thank you for all your contributions Roy! ]]> Wed, 22 May 2013 19:47:01 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02436.html portal-noreply@xxxxxxx (portal on behalf of emo) [pdt-dev] Commit rights for David Kelsey have been expired http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02435.html tools.pdt Committers, Jacek Pospychala has expired the commit rights for David Kelsey (dkelsey). The reason for this change is: Removing commit rights for David who hasn't been actively developing PDT for last few years. David thank you for your significan... tools.pdt Committers, Jacek Pospychala has expired the commit rights for David Kelsey (dkelsey). The reason for this change is: Removing commit rights for David who hasn't been actively developing PDT for last few years. David thank you for your significant contributions in PDT! ]]> Wed, 22 May 2013 19:46:01 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02435.html portal-noreply@xxxxxxx (portal on behalf of emo) [pdt-dev] Commit rights for Shalom Gibly have been expired http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02434.html tools.pdt Committers, Jacek Pospychala has expired the commit rights for Shalom Gibly (sgibly). The reason for this change is: Removing commit rights for Shalom who hasn't been actively involved in PDT development in last few years. Thank you for your cont... tools.pdt Committers, Jacek Pospychala has expired the commit rights for Shalom Gibly (sgibly). The reason for this change is: Removing commit rights for Shalom who hasn't been actively involved in PDT development in last few years. Thank you for your contributions Shalom! ]]> Wed, 22 May 2013 19:43:02 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02434.html portal-noreply@xxxxxxx (portal on behalf of emo) [pdt-dev] Commit rights for Q.S. Wang have been expired http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02433.html tools.pdt Committers, Jacek Pospychala has expired the commit rights for Q.S. Wang (qiwang). The reason for this change is: Removing commit rights for Qiangsheng who hasn't been actively developing PDT for last few years. Thank you for your contributions Q... tools.pdt Committers, Jacek Pospychala has expired the commit rights for Q.S. Wang (qiwang). The reason for this change is: Removing commit rights for Qiangsheng who hasn't been actively developing PDT for last few years. Thank you for your contributions Q.S.! ]]> Wed, 22 May 2013 19:42:01 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02433.html portal-noreply@xxxxxxx (portal on behalf of emo) [pdt-dev] Commit rights for Nick Boldt have been expired http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02432.html tools.pdt Committers, Jacek Pospychala has expired the commit rights for Nick Boldt (nickb). The reason for this change is: Removing commit rights for Nick who has been leading PDT releng long time ago in ages of PDT Build and Athena. Thank you for your wo... tools.pdt Committers, Jacek Pospychala has expired the commit rights for Nick Boldt (nickb). The reason for this change is: Removing commit rights for Nick who has been leading PDT releng long time ago in ages of PDT Build and Athena. Thank you for your work Nick! ]]> Wed, 22 May 2013 19:36:01 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02432.html portal-noreply@xxxxxxx (portal on behalf of emo) [pdt-dev] [Hudson] Hudson build became unstable: pdt-master #79 http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02431.html See &lt;https://hudson.eclipse.org/hudson/job/pdt-master/79/changes&gt; -- This message is automatically generated by Hudson. For more information on Hudson, see: http://hudson-ci.org/ See <https://hudson.eclipse.org/hudson/job/pdt-master/79/changes> -- This message is automatically generated by Hudson. For more information on Hudson, see: http://hudson-ci.org/ ]]> Tue, 21 May 2013 19:37:37 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02431.html hudsonbuild@xxxxxxx (hudsonbuild) Re: [pdt-dev] Code formatter contribution for PDT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02430.html It's great, I missed region based formatter a lot :). One minor thing, I use UI Theme Feature and dark background, it's seems that formatter keep colors for text but not for background and preview is not relevant (white text on white background in my situa... It's great, I missed region based formatter a lot :). One minor thing, I use UI Theme Feature and dark background, it's seems that formatter keep colors for text but not for background and preview is not relevant (white text on white background in my situation).

Marek Maksimczyk



]]> Tue, 21 May 2013 15:18:20 GMT http://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02430.html marek.maksimczyk@xxxxxxx (Marek Maksimczyk)