Hey DLTK project!
Participation in the simultaneous release requires that at least one
project member monitor the cross-project-issues-dev mailing list.
Since there has been no response from DLTK to my requests for
action, I have to assume that this has been overlooked. Can somebody
from the project please subscribe to this list?
Also, I need the DLTK project to update their release information in
the project metadata.
http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata
Minimally, I need you to create a release record for the Kepler
release. Please also make sure that the project plan is up-to-date
(you can now enter this directly into the release record in the
project metadata).
The project downloads page doesn't list any 5.0 milestone builds.
The build aggregator for Kepler indicates that DLTK is pulling in
4.0
Please be advised that I am now applying greater scrutiny to release
requirements during release reviews. I've made a few clarifying
updates to the Release Review checklist (note that no new
requirements have been added).
http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist
Let me know if you require any assistance.
Thanks,
Wayne
-------- Original Message --------
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