[cross-project-issues-dev] 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 e...@eclipse.org. 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 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews
Hi Found it. It's lurking on the left of http://eclipse.org/projects/tools/ip_contribution_review.php, so if you ignore the rubbish from http://eclipse.org/projects/tools/ip_contribution_review.php you get the good old review. Regards Ed Willink On 17/05/2013 07:18, Ed Willink wrote: Hi What has happened to the old (very good) IP tool? It gave me a good auto-generated log for MDT/OCL that I could easily review. http://eclipse.org/projects/tools/ip_contribution_review.php is hard to find (no link from portal or project page) and gives me a list of over 600 bugs to review. No way. There have been zero IP contributions so I expect to do the job in 10 minutes not 10 hours. If there really is a change in diligence then please threshold it at resolution after Juno, since all pre-Juno bugs have been IP logged and approved. Regards Ed Willink On 26/04/2013 19:24, The Eclipse Foundation wrote: Kepler approaches. I'm starting to get IP Log review requests for the upcoming release. In at least two cases, I'm pretty sure that the submitter thought that the release date was in May. To be clear, here are the dates: May 24/2013 - Deadline to submit IP Logs for Kepler releases June 5/2013 - PMC-approved Review materials submitted to EMO June 12/2013 - Kepler Uber Release review June 26/2013 - Kepler release The IP Logs are not due for another month. It's still a little early, but it's perfectly acceptable to submit your IP log for review in advance of the actual required-by date. Just keep in mind that the log needs to accurately reflect the content that you're releasing; if you anticipate receiving any contributions from folks who are not committers, it might be a good idea to hold off for a while. While I'm at it, I'd like to make a plea to everybody to please try and honour the dates specified. There are a few projects that make a habit of submitting the required materials late; this causes a lot of stress for everybody involved. If you haven't started thinking about your IP Log and review documentation, now might be a good time to do so. I need to have you PMC-approved review documentation before EOB on June 5/2013. You can either do what we've been doing for years and submit this information as a presentation, document, PDF, or whatever. Or you can just enter review information directly in the release record in the Project Management Infrastructure. A few of you have already started doing the latter; my sense is that it is an easy way to assemble and provide this information. Please let me know if you think otherwise, or if there is anything that we can do to improve it. The PMC approval part is important. Get it approved. This may take some time. Plan to engage your PMC at least a full week in advance of the June 5 deadline. PMC members, please make sure that the document is complete and that you are satisfied with its content before providing your approval. When I look at the extremely short (or non-existent) "outside contributions" sections on some IP logs, I grow concerned that some projects aren't doing enough to court the community and grow diversity. Please use the Release Review checklist to make sure that you've done all the necessary bits: http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist Note that this checklist has been around for a long time. There should be nothing new or surprising here. I've noticed that a lot of projects do not have plans posted. This is an important and necessary part of the development process. Plan information can be entered directly in the release record in the Project Management Infrastructure. Providing a project plan in a standard format is required. Wrestling with XML is no longer required. It's easy. Please make this happen. Note that planning should happen at the beginning of a release cycle. PMCs, please impress the importance of this on your projects. Thanks, Wayne -- Wayne Beaton on behalf of the Eclipse Foundation ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org
Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews
I opened a ticket some time ago, proposing to have the link on the project page: https://bugs.eclipse.org/bugs/show_bug.cgi?id=400551 I guess it will be then easy to find. Krum From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed Willink Sent: Freitag, 17. Mai 2013 08:26 To: Cross project issues Subject: Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews Hi Found it. It's lurking on the left of http://eclipse.org/projects/tools/ip_contribution_review.php, so if you ignore the rubbish from http://eclipse.org/projects/tools/ip_contribution_review.php you get the good old review. Regards Ed Willink On 17/05/2013 07:18, Ed Willink wrote: Hi What has happened to the old (very good) IP tool? It gave me a good auto-generated log for MDT/OCL that I could easily review. http://eclipse.org/projects/tools/ip_contribution_review.php is hard to find (no link from portal or project page) and gives me a list of over 600 bugs to review. No way. There have been zero IP contributions so I expect to do the job in 10 minutes not 10 hours. If there really is a change in diligence then please threshold it at resolution after Juno, since all pre-Juno bugs have been IP logged and approved. Regards Ed Willink On 26/04/2013 19:24, The Eclipse Foundation wrote: Kepler approaches. I'm starting to get IP Log review requests for the upcoming release. In at least two cases, I'm pretty sure that the submitter thought that the release date was in May. To be clear, here are the dates: May 24/2013 - Deadline to submit IP Logs for Kepler releases June 5/2013 - PMC-approved Review materials submitted to EMO June 12/2013 - Kepler Uber Release review June 26/2013 - Kepler release The IP Logs are not due for another month. It's still a little early, but it's perfectly acceptable to submit your IP log for review in advance of the actual required-by date. Just keep in mind that the log needs to accurately reflect the content that you're releasing; if you anticipate receiving any contributions from folks who are not committers, it might be a good idea to hold off for a while. While I'm at it, I'd like to make a plea to everybody to please try and honour the dates specified. There are a few projects that make a habit of submitting the required materials late; this causes a lot of stress for everybody involved. If you haven't started thinking about your IP Log and review documentation, now might be a good time to do so. I need to have you PMC-approved review documentation before EOB on June 5/2013. You can either do what we've been doing for years and submit this information as a presentation, document, PDF, or whatever. Or you can just enter review information directly in the release record in the Project Management Infrastructure. A few of you have already started doing the latter; my sense is that it is an easy way to assemble and provide this information. Please let me know if you think otherwise, or if there is anything that we can do to improve it. The PMC approval part is important. Get it approved. This may take some time. Plan to engage your PMC at least a full week in advance of the June 5 deadline. PMC members, please make sure that the document is complete and that you are satisfied with its content before providing your approval. When I look at the extremely short (or non-existent) outside contributions sections on some IP logs, I grow concerned that some projects aren't doing enough to court the community and grow diversity. Please use the Release Review checklist to make sure that you've done all the necessary bits: http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist Note that this checklist has been around for a long time. There should be nothing new or surprising here. I've noticed that a lot of projects do not have plans posted. This is an important and necessary part of the development process. Plan information can be entered directly in the release record in the Project Management Infrastructure. Providing a project plan in a standard format is required. Wrestling with XML is no longer required. It's easy. Please make this happen. Note that planning should happen at the beginning of a release cycle. PMCs, please impress the importance of this on your projects. Thanks, Wayne -- Wayne Beaton on behalf of the Eclipse Foundationhttp://www.eclipse.org/ [EclipseCon France 2013]http://www.eclipsecon.org/france2013 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2013.0.3272 / Virus Database: 3162/6275 - Release Date: 04/26/13
Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews
The contribution review tool is intended to assist a project in identifying IP contributions that come through Bugzilla. If your project is using Git and is pushing commits that are correctly annotated with author information, then this tool will be of no interest to you. Its main value at this point is mostly historical for most projects. I'll add a link to the IP Log generator from the project page. HTH, Wayne On 05/17/2013 02:26 AM, Ed Willink wrote: Hi Found it. It's lurking on the left of http://eclipse.org/projects/tools/ip_contribution_review.php, so if you ignore the rubbish from http://eclipse.org/projects/tools/ip_contribution_review.php you get the good old review. Regards Ed Willink On 17/05/2013 07:18, Ed Willink wrote: Hi What has happened to the old (very good) IP tool? It gave me a good auto-generated log for MDT/OCL that I could easily review. http://eclipse.org/projects/tools/ip_contribution_review.php is hard to find (no link from portal or project page) and gives me a list of over 600 bugs to review. No way. There have been zero IP contributions so I expect to do the job in 10 minutes not 10 hours. If there really is a change in diligence then please threshold it at resolution after Juno, since all pre-Juno bugs have been IP logged and approved. Regards Ed Willink On 26/04/2013 19:24, The Eclipse Foundation wrote: Kepler approaches. I'm starting to get IP Log review requests for the upcoming release. In at least two cases, I'm pretty sure that the submitter thought that the release date was in May. To be clear, here are the dates: May 24/2013 - Deadline to submit IP Logs for Kepler releases June 5/2013 - PMC-approved Review materials submitted to EMO June 12/2013 - Kepler Uber Release review June 26/2013 - Kepler release The IP Logs are not due for another month. It's still a little early, but it's perfectly acceptable to submit your IP log for review in advance of the actual required-by date. Just keep in mind that the log needs to accurately reflect the content that you're releasing; if you anticipate receiving any contributions from folks who are not committers, it might be a good idea to hold off for a while. While I'm at it, I'd like to make a plea to everybody to please try and honour the dates specified. There are a few projects that make a habit of submitting the required materials late; this causes a lot of stress for everybody involved. If you haven't started thinking about your IP Log and review documentation, now might be a good time to do so. I need to have you PMC-approved review documentation before EOB on June 5/2013. You can either do what we've been doing for years and submit this information as a presentation, document, PDF, or whatever. Or you can just enter review information directly in the release record in the Project Management Infrastructure. A few of you have already started doing the latter; my sense is that it is an easy way to assemble and provide this information. Please let me know if you think otherwise, or if there is anything that we can do to improve it. The PMC approval part is important. Get it approved. This may take some time. Plan to engage your PMC at least a full week in advance of the June 5 deadline. PMC members, please make sure that the document is complete and that you are satisfied with its content before providing your approval. When I look at the extremely short (or non-existent) "outside contributions" sections on some IP logs, I grow concerned that some projects aren't doing enough to court the community and grow diversity. Please use the Release Review checklist to make sure that you've done all the necessary bits: http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist Note that this checklist has been around for a long time. There should be nothing new or surprising here. I've noticed that a lot of projects do not have plans posted. This is an important and necessary part of the development
[cross-project-issues-dev] Kepler dates, IP Logs, and reviews
Kepler approaches. I'm starting to get IP Log review requests for the upcoming release. In at least two cases, I'm pretty sure that the submitter thought that the release date was in May. To be clear, here are the dates: May 24/2013 - Deadline to submit IP Logs for Kepler releases June 5/2013 - PMC-approved Review materials submitted to EMO June 12/2013 - Kepler Uber Release review June 26/2013 - Kepler release The IP Logs are not due for another month. It's still a little early, but it's perfectly acceptable to submit your IP log for review in advance of the actual required-by date. Just keep in mind that the log needs to accurately reflect the content that you're releasing; if you anticipate receiving any contributions from folks who are not committers, it might be a good idea to hold off for a while. While I'm at it, I'd like to make a plea to everybody to please try and honour the dates specified. There are a few projects that make a habit of submitting the required materials late; this causes a lot of stress for everybody involved. If you haven't started thinking about your IP Log and review documentation, now might be a good time to do so. I need to have you PMC-approved review documentation before EOB on June 5/2013. You can either do what we've been doing for years and submit this information as a presentation, document, PDF, or whatever. Or you can just enter review information directly in the release record in the Project Management Infrastructure. A few of you have already started doing the latter; my sense is that it is an easy way to assemble and provide this information. Please let me know if you think otherwise, or if there is anything that we can do to improve it. The PMC approval part is important. Get it approved. This may take some time. Plan to engage your PMC at least a full week in advance of the June 5 deadline. PMC members, please make sure that the document is complete and that you are satisfied with its content before providing your approval. When I look at the extremely short (or non-existent) "outside contributions" sections on some IP logs, I grow concerned that some projects aren't doing enough to court the community and grow diversity. Please use the Release Review checklist to make sure that you've done all the necessary bits: http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist Note that this checklist has been around for a long time. There should be nothing new or surprising here. I've noticed that a lot of projects do not have plans posted. This is an important and necessary part of the development process. Plan information can be entered directly in the release record in the Project Management Infrastructure. Providing a project plan in a standard format is required. Wrestling with XML is no longer required. It's easy. Please make this happen. Note that planning should happen at the beginning of a release cycle. PMCs, please impress the importance of this on your projects. Thanks, Wayne -- Wayne Beaton on behalf of the Eclipse Foundation ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Kepler dates
Here are the Kepler dates: 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 Thanks, Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
