Re: [cross-project-issues-dev] Missing release information for some Kepler projects
On Wed, Jun 12, 2013 at 12:47 AM, Ralf Sternberg rsternb...@eclipsesource.com wrote: I don't know about the SRs but I remember that EGit updated from 1.3 to 2.0 in Juno RC2 or RC3. For me this feels like a pretty risky change for an RC. I don't mean to point the finger at EGit, I just think we should agree that RC1 should really be a release candidate, i.e. almost the thing that is going to be released except for some minor fixes. The code should cool down after that point. At least major versions should not change anymore. I agree we should contribute to the release train earlier than that. Due to our faster release cycle (4 releases per year) M6 is usually shortly after our previous release in the same year. Hence for Kepler we did the first 3.0 contribution with M7. AFAIK those who depend on us know our nightly build, watch code reviews and discussions on our mailing lists and speak up early in case they see a problem. -- Matthias ___ 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] Missing release information for some Kepler projects
On Tue, Jun 11, 2013 at 11:13 PM, Ed Willink e...@willink.me.uk wrote: Hi I think a certain amount of self-policing is possible for the many 'minor' projects. Their consumers are surely well aware how stable builds are and how much credible development is going on. Concerned projects should perhaps contact the EMO at M6 to complain about the lack of M4 project plan and request a firm commitment to either a frozen/point/minor/major release. For 'major' projects I'm not sure what can be done. Surely EGIT has enough experienced committers to know that a major new release at SR2 RC3 is not the way maintenance is done? Perhaps the EMO should enforce only PMC-approved major or point version changes after M6, and AB-approved after M7. NB thais includes SR1 and SR2 that should be maintence. If there is a new release it is new not maintenance. I am not aware of any EGit major release we would have done for a SR2. We release roughly every 3 months and we don't have the bandwidth to maintain several versions in parallel. So far we did major versions with SR0 and delivered minor version releases with SR1, SR2 and an additional one in Dec. -- Matthias ___ 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] Missing release information for some Kepler projects
I don't know about the SRs but I remember that EGit updated from 1.3 to 2.0 in Juno RC2 or RC3. For me this feels like a pretty risky change for an RC. I don't mean to point the finger at EGit, I just think we should agree that RC1 should really be a release candidate, i.e. almost the thing that is going to be released except for some minor fixes. The code should cool down after that point. At least major versions should not change anymore. Ralf ___ 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] Missing release information for some Kepler projects
I recall the planning council recently decided on a policy that we would not allow a new release of a project to appear for the first time after RC1. Am I remembering that incorrectly? This is exactly the kind of last minute change that caused trouble for the release train in Juno SR2. I think at this point they should be contributing the same release that was contributed in RC1, which sounds like 4.0. John From: David M Williams david_willi...@us.ibm.com To: Cross project issues cross-project-issues-dev@eclipse.org, Date: 06/07/2013 09:52 AM Subject:Re: [cross-project-issues-dev] Missing release information for some Kepler projects Sent by:cross-project-issues-dev-boun...@eclipse.org I agree its not cool. I do not know their reasons for it. I do recall them sending a note a month or two ago asking for preferences ... so suggest you and DLTK project work out which is best (for you to move to 5.x or them to revert to 4.x). There should only be one version major version in the common repository. Good luck, From:Benjamin Cabé bc...@sierrawireless.com To:Cross project issues cross-project-issues-dev@eclipse.org, Date:06/07/2013 09:40 AM Subject:Re: [cross-project-issues-dev] Missing release information for some Kepler projects Sent by:cross-project-issues-dev-boun...@eclipse.org Hi, Contributing DLTK 5.0 and removing 4.0 at the very last minute (RC3) to the Kepler repo with no previous contribution before that would have allowed Koneki Lua Development Tools to be tested against it, is not really cool to say the least. LDT contribution to Kepler is now broken. Any chance to also include DLTK 4.0 into the Kepler repo? Thanks. Benjamin-- De : Alexey Panchenko alex.panche...@gmail.com Répondre à : Cross project issues cross-project-issues-dev@eclipse.org Date : jeudi 9 mai 2013 17:49 À : Cross project issues cross-project-issues-dev@eclipse.org Objet : Re: [cross-project-issues-dev] Missing release information for some Kepler projects Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- 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
Re: [cross-project-issues-dev] Missing release information for some Kepler projects
Hi, I've finally managed to updated DLTK contribution to the latest build. When it will be picked up by the release process, to verify the results? Regards, Alex On Fri, May 10, 2013 at 12:52 PM, Jacek Pospychała jacek.pospych...@gmail.com wrote: hi, PDT has been building and testing against DLTK-nightly builds for last months, so we prefer DLTK 5.0. thanks, Jacek On Thu, May 9, 2013 at 5:49 PM, Alexey Panchenko alex.panche...@gmail.com wrote: Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. *I will not accept review documentation for any release that is not recorded in the project metadata.* While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ 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 mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 480x60.pngimage/png___ 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] Missing release information for some Kepler projects
I'll turn aggregator back on on Friday ... but ... projects can verify their own stuff, without waiting for the main aggregation build. See http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_Running_Locally From: Alexey Panchenko alex.panche...@gmail.com To: Cross project issues cross-project-issues-dev@eclipse.org, Date: 06/06/2013 08:36 AM Subject:Re: [cross-project-issues-dev] Missing release information for some Kepler projects Sent by:cross-project-issues-dev-boun...@eclipse.org Hi, I've finally managed to updated DLTK contribution to the latest build. When it will be picked up by the release process, to verify the results? Regards, Alex On Fri, May 10, 2013 at 12:52 PM, Jacek Pospychała jacek.pospych...@gmail.com wrote: hi, PDT has been building and testing against DLTK-nightly builds for last months, so we prefer DLTK 5.0. thanks, Jacek On Thu, May 9, 2013 at 5:49 PM, Alexey Panchenko alex.panche...@gmail.com wrote: Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- 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 -- 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 _ __ 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 mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _ __ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev image/pngimage/png___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https
Re: [cross-project-issues-dev] Missing release information for some Kepler projects
Hi, we would like to have RTP dropped form the release train. I will delete the b3 aggregator file today. Thansk in advance. Cheers Holger On May 10, 2013, at 7:52 AM, Jacek Pospychała jacek.pospych...@gmail.com wrote: hi, PDT has been building and testing against DLTK-nightly builds for last months, so we prefer DLTK 5.0. thanks, Jacek On Thu, May 9, 2013 at 5:49 PM, Alexey Panchenko alex.panche...@gmail.com wrote: Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects Mail Attachment.png ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation Learn about Eclipse Projects 480x60.png ___ 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 mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Holger Staudacher Follow me: @hstaudacher Innoopract Informationssysteme GmbH hstaudac...@eclipsesource.com Tel: +49 721 - 66 47 33 - 0 Fax: +49 721 - 66 47 33 29 = Legal Disclaimer = According to Section 80 of the German Corporation Act Innoopract Informationssysteme GmbH must indicate the following information: Address: Lammstr. 21, 76133 Karlsruhe Germany General Manager: Jochen Krause Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org
Re: [cross-project-issues-dev] Missing release information for some Kepler projects
hi, PDT has been building and testing against DLTK-nightly builds for last months, so we prefer DLTK 5.0. thanks, Jacek On Thu, May 9, 2013 at 5:49 PM, Alexey Panchenko alex.panche...@gmail.comwrote: Hi, Unfortunately The DLTK team were quite busy this year with other projects. Initially the previous (4.0, released 2012) version was added to Kepler, with the intent to replace it later with the 5.0 builds from master. So far, that did not happen yet, partly because of source control (- git) build system (- tycho) changes. AFAIK DLTK is used by PDT and Koneki-Lua Development Tools. So the question to these projects: what DLTK version would you prefer in Kepler? Regards, Alex On Thu, May 9, 2013 at 12:26 AM, Wayne Beaton wa...@eclipse.org wrote: I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. *I will not accept review documentation for any release that is not recorded in the project metadata.* While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ 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 mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 480x60.pngimage/png___ 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] Missing release information for some Kepler projects
I am now only missing the information for the DLTK and Runtime Packaging (RTP) project. I have contacted DLTK via their mailing list; Ian has contacted the RTP project leaders directly (thanks, Ian). I noticed that DLTK is contributing their 4.0 release build (from Juno) to Kepler, despite there being some apparent activity in the project Git repositories. I don't know if there is any specific issue with this, but thought that I'd point it out in case any downstream consumers had any concerns/issues. Thanks, Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- 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 -- 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] Missing release information for some Kepler projects
We're getting closer. I've been able to remove a few entries from this list. I'm still missing release version records/declarations from a few projects. Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform I am starting to have concern that either these projects do not have representation on the cross-projects list. Participation in the communication is a requirement for participation in the simultaneous. Please let the group know if you're getting these messages but just refuse to do anything about them. If you require assistance, please let me know. If asking you to create a release record is too much to ask, please let me know. By way of reminder, here is a link to release review requirements. http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews Please review the checklist to ensure that you're getting all the required bits done. There should be nothing new here. Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- 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 -- 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] Missing release information for some Kepler projects
Wayne, I'll update the Maven Integration for Web Tools Platform metadata as soon as I can, in the next couple days. Regards, Fred Bricon On Mon, Apr 29, 2013 at 6:02 PM, Wayne Beaton wa...@eclipse.org wrote: We're getting closer. I've been able to remove a few entries from this list. I'm still missing release version records/declarations from a few projects. Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform I am starting to have concern that either these projects do not have representation on the cross-projects list. Participation in the communication is a requirement for participation in the simultaneous. Please let the group know if you're getting these messages but just refuse to do anything about them. If you require assistance, please let me know. If asking you to create a release record is too much to ask, please let me know. By way of reminder, here is a link to release review requirements. http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews Please review the checklist to ensure that you're getting all the required bits done. There should be nothing new here. Wayne On 04/26/2013 02:38 PM, Wayne Beaton wrote: I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. *I will not accept review documentation for any release that is not recorded in the project metadata.* While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundationhttp://www.eclipse.org Learn about Eclipse Projects http://www.eclipse.org/projects [image: EclipseCon France 2013] http://www.eclipsecon.org/france2013 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Have you tried turning it off and on again - The IT Crowd Title: Re: [cross-project-issues-dev] Missing release information for some Kepler projects We're getting closer. I've been able to remove a few entries from this list. I'm still missing release version records/declarations from a few projects. Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform I am starting to have concern that either these projects do not have representation on the cross-projects list. Participation in the communication is a requirement for participation in the simultaneous. Please let the group know if you're getting these messages but just refuse to do anything about them. If you require assistance, please let me know. If asking you to create a release record is too much to ask, please let me know
[cross-project-issues-dev] Missing release information for some Kepler projects
I am missing release information for the following projects that have declared intent to participate in Kepler. C/C++ Development Tools (CDT) Dynamic Languages Toolkit (DLTK) Eclipse Modeling Framework (EMF) Eclipse Communication Framework (ECF) Runtime Packaging Project (RTP) EclipseLink Ecore Tools Extended Editing Framework (EEF) Jubula Functional Testing Tool MDT XSD (XML Schema Definition) Maven Integration for Web Tools Platform SCA Tools In some cases, it may be that I just can't sort out what release you want to include, or maybe you're planning to include a release that does not occur on the Kepler release date (which I find weird, but is otherwise okay). If you have not done so already, please visit your project's information page and create a release record for Kepler and then please let me know either on this list or via direct email so that I can update the Kepler release page. I will not accept review documentation for any release that is not recorded in the project metadata. While you're there, please take a few minutes to update the description and plan information for your release. The description should be a short paragraph that concisely describes the high points of the release. Note that you can still use the old XML-file based plan format if you like using old and painful technology. You can quickly get access to your project's information page directly from the Kepler release page: https://projects.eclipse.org/releases/kepler Let me know if you require any assistance. Wayne -- 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
