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
