You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Konrad Windszus <ko...@netcentric.biz> on 2017/04/27 13:39:26 UTC
Release of new Sling Eclipse IDE
IMHO quite some issues have been fixed for the Sling Eclipse IDE, most notably https://issues.apache.org/jira/browse/SLING-6112, https://issues.apache.org/jira/browse/SLING-6618 and https://issues.apache.org/jira/browse/SLING-5634. At least the last two ones I consider quite serious. All issues which already have been fixed are in https://issues.apache.org/jira/browse/SLING-6519?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Sling%20Eclipse%20IDE%201.2.0%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC.
It would be nice to fix https://issues.apache.org/jira/browse/SLING-6255 as well, but that has a dependency on the outstanding release of Tooling Support Source 1.0.2. I will start the release vote on the latter soon.
Is there any other outstanding issue which should end up in Sling IDE 1.2.0?
@Robert: Would you be able to take care of the release, as I am not really familiar with the code signing process?
Konrad
Re: Release of new Sling Eclipse IDE
Posted by Robert Munteanu <ro...@apache.org>.
On Thu, 2017-04-27 at 15:39 +0200, Konrad Windszus wrote:
> IMHO quite some issues have been fixed for the Sling Eclipse IDE,
> most notably https://issues.apache.org/jira/browse/SLING-6112,
> https://issues.apache.org/jira/browse/SLING-6618 and
> https://issues.apache.org/jira/browse/SLING-5634. At least the last
> two ones I consider quite serious. All issues which already have been
> fixed are in https://issues.apache.org/jira/browse/SLING-
> 6519?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Sling%20
> Eclipse%20IDE%201.2.0%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY
> %20priority%20DESC.
>
> It would be nice to fix https://issues.apache.org/jira/browse/SLING-6
> 255 as well, but that has a dependency on the outstanding release of
> Tooling Support Source 1.0.2. I will start the release vote on the
> latter soon.
>
> Is there any other outstanding issue which should end up in Sling IDE
> 1.2.0?
> @Robert: Would you be able to take care of the release, as I am not
> really familiar with the code signing process?
Code signing is not re-implemented based on the ASF code signing
service right now.
We can either wait and try to implement - I have some untested POC code
for that or release without code signing.
Robert
>
> Konrad