Re: [cross-project-issues-dev] Missing release information for some Kepler projects

[Fred Bricon]

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 
> Foundation<http://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 
> Foundation<http://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. By way of reminder, here is a link to release review requirements. http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews Please revi 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