Re: [technology-pmc] [cross-project-issues-dev] Missing release informat

[Benjamin Cabé <bcabe@xxxxxxxxxxxxxxxxxx>]

Hi,

As I just mentioned on the cross-projects mailing-list, we should be fine for Kepler, and we will switch to DLTK 5.

However, there are several points I'd like to raise here for public discussion …and sorry if this will look like finger-pointing :-/

• AFAICT there has been no DLTK5 p2 repo available before June 6, therefore I am not quite sure how we were supposed to consume DLTK5 from our Tycho build
• There has been no contribution to Kepler before June 6. Even if not as bad last year (a January I-build was in Juno already), it already happened and was quite annoying [0] 
• It's rather unclear what is the project plan (actually I can't even find it), especially in terms of milestone releases.
• As far as I can tell, there were only 10 bugs resolved for this release [1], and actually only 5 in the Core framework. This is actually a good sign that the technology is mature (well, we have several bug we reported who just never received attention though [2]), therefore I am having troubles understanding why API breaks were introduced. The release document for 5.0 indicates that "DLTK 5.0 did not introduced significant features, but the team was focused on project stability, API refinements, performance improvements and adopters support". I am not quite sure this is a good practice to refine API just for the sake of refining API, especially that late in the game.

For next year, I would really like to see a project plan shared earlier with the community, and I would like not to see a DLTK 6.0 which just randomly changes API instead of working with adopters to improve the current framework.

Thanks.

Benjamin-- 

[0] http://dev.eclipse.org/mhonarc/lists/dltk-dev/msg02218.html

[1] https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=bug_status&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=DLTK&longdesc_type=allwordssubstr&longdesc="">

[2] https://bugs.eclipse.org/bugs/buglist.cgi?f1=longdescs.count&emailreporter1=1&list_id=5847224&o1=equals&emailtype1=substring&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&email1=sierra&v1=1&component=Common&component=Common-Debug&product=DLTK 

De : Alexey Panchenko <alex.panchenko@xxxxxxxxx>
Date : vendredi 7 juin 2013 17:53
À : Wayne Beaton <wayne@xxxxxxxxxxx>, Benjamin CABE <BCabe@xxxxxxxxxxxxxxxxxx>, Jacek Pospychała <jacek.pospychala@xxxxxxxxx>
Cc : Andrey Sobolev <haiodo@xxxxxxxxx>, "technology-pmc@xxxxxxxxxxx" <technology-pmc@xxxxxxxxxxx>
Objet : Re: Re: [cross-project-issues-dev] Missing release information for some Kepler projects

Hi,

Sorry for the late changes. Unfortunately, DLTK team was lacking resources this year.

It happened that PDT was developed against master/5.0 and LDT against previous/4.0

Actually, DLTK versions are mostly compatible (like 99%). however formally version must be increased e.g. after some deprecated member was removed, etc.

Andrey just built LDT against latest DLTK (updated dependencies and fixed a couple of compilation errors) - see the attached patch.

Regards,

Alex

On Fri, Jun 7, 2013 at 9:03 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:

Alex and Andrey,

Please work with Benjamin and Jacek to sort out this issue.

Thanks,

Wayne

-------- Original Message --------

Subject:	Re: [cross-project-issues-dev] Missing release information for some Kepler projects
Date:	Fri, 7 Jun 2013 06:39:27 -0700
From:	Benjamin Cabé <bcabe@xxxxxxxxxxxxxxxxxx>
Reply-To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

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.panchenko@xxxxxxxxx>
Répondre à : Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date : jeudi 9 mai 2013 17:49
À : Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
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 <wayne@xxxxxxxxxxx> 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@xxxxxxxxxxxhttps://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@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects