[
https://issues.apache.org/jira/browse/SLING-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3620.
------------------------------------
Resolution: Fixed
* http://svn.apache.org/viewvc?view=revision&revision=1604753 - generate a
source zip file which can be used for release voting
* http://svn.apache.org/viewvc?view=revision&revision=1604754 - fix
category.xml to be independent of the project's verstion
* http://svn.apache.org/viewvc?view=revision&revision=1604756 - bump the
version to 1.0.0
* http://svn.apache.org/viewvc?view=revision&revision=1604757 - force the
qualifier to be 'RELEASE' in preparation for the release.
I filed SLING-3685 to follow-up with more release engineering improvements.
> POM preparations for release
> ----------------------------
>
> Key: SLING-3620
> URL: https://issues.apache.org/jira/browse/SLING-3620
> Project: Sling
> Issue Type: Task
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The POMs we use are working for regular building, but they must be tweaked a
> bit before releasing. Some ( probably non-exhaustive ) notes
> * scm settings for all projects
> * ensure that gpg signing is performed when releasing
> * ensure that p2 signing is performed when releasing
> It seems that we can use the ASF parent pom , unlike the Sling parent pom.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
