[
https://issues.apache.org/jira/browse/SLING-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954570#comment-17954570
]
Robert Munteanu commented on SLING-8307:
----------------------------------------
I don't have a strong opinion (anymore) on what needs to be done for signing.
What is still mising from SLING-11680? I can build the p2 update site locally
using my GPG key and the signature is properly shown when installing in Eclipse.
> Update the Eclipse tooling release process after the restructuring and code
> signing changes
> -------------------------------------------------------------------------------------------
>
> Key: SLING-8307
> URL: https://issues.apache.org/jira/browse/SLING-8307
> Project: Sling
> Issue Type: Task
> Components: IDE
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Sling Eclipse IDE 1.3.0
>
>
> We introduced some significant changes since the last release:
> - we restructured the modules in SLING-5648
> - we updated the code signing mechanism in SLING-10064 (but also note
> SLING-11680 )
> Additionally, with Tycho 1.1.0 a [release workflow based on the
> maven-release-plugin|https://wiki.eclipse.org/Tycho/Release_Workflow] is
> possible.
> Taking all of these into account we should update the release process and the
> [associated
> documentation|https://sling.apache.org/documentation/development/release-management.html#releasing-the-sling-ide-tooling-1]
> .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
