Both 1.3 and 2.0 as next version is fine for me.
Konrad
> On 11. Apr 2025, at 17:03, Robert Munteanu <romb...@apache.org> wrote:
>
> On Wed, 2023-08-30 at 09:37 +0200, Konrad Windszus wrote:
>> Hi Robert,
>> This plan sounds good to me.
>> Let me know in case of questions related to signing:
>> https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+-+Signing
>> We should definitely switch to GPG signing in the midterm as that is
>> built into Tycho (https://issues.apache.org/jira/browse/SLING-11680)
>> but I haven’t tried it out yet.
>> Thanks for taking it up,
>> Konrad
>
> In the meantime I managed to apply some fixes for Windows support and I
> think we should be at least at the same level as before the big
> refactoring.
>
> There are now 4 issues targeted for 2.0 [1], 2 of which are about the
> release process and automation. I would not add anything else unless
> it's a show-stopper and start the release process once we have the code
> fixes in.
>
> I would also reconsider the plan to call this release 2.0 because it
> really does not change anything fundamental for the user. Yes, we did
> the big split and now have a more flexible API that other IDEs can use
> but this is not a user-facing benefit in any way. My proposal is for
> the next release to be 1.3.0 instead.
>
> Thoughts?
>
> Thanks,
> Robert
>
> [1]:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Sling%20Eclipse%20IDE%202.0.0%22%20and%20resolution%20is%20empty
