[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040663#comment-14040663 ] 

Robert Munteanu edited comment on SLING-3685 at 7/1/14 2:42 PM:
----------------------------------------------------------------

For reference, this is the current release process, assuming that the current version is 1.0.1-SNAPSHOT

* set the fix version as released: {{mvn tycho-versions:set-version -DnewVersion=1.0.2}}
* commit the change to svn
* manually tag in svn {{svn copy https://svn.apache.org/repos/asf/sling/trunk/tooling/ide https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2}}
* deploy the project with p2/gpg signing enabled {{mvn clean deploy -Psign,!eclipse-test}} ( alternatively {{mvn clean deploy -Psign,\!eclipse-test}} to make bash happy) 
* inspect the staging repository from nexus to ensure that all artifacts are properly deployed
* call the vote
* Update to next version, e.g. {{mvn tycho-versions:set-version -DnewVersion=1.0.3-SNAPSHOT}}

Once the release has passed, the following must be done:

* upload p2update.zip* to https://dist.apache.org/repos/dist/release/sling/
* upload unzipped update site to https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
* update https://dist.apache.org/repos/dist/release/sling/eclipse/composite{Content,Artifacts}.xml to point to the latest $VERSION ( remove old one )
* (TODO how?) archive the old artifact versions but leave pointers to archive.apache.org 


was (Author: rombert):
For reference, this is the current release process, assuming that the current version is 1.0.1-SNAPSHOT

* set the fix version as released: {{mvn tycho-versions:set-version -DnewVersion=1.0.2}}
* commit the change to svn
* manually tag in svn {{svn copy https://svn.apache.org/repos/asf/sling/trunk/tooling/ide https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2}}
* deploy the project with p2/gpg signing enabled {{mvn clean deploy -Psign,!eclipse-test}} ( alternatively {{mvn clean deploy -Psign,\!eclipse-test}} to make bash happy) 
* inspect the staging repository from nexus to ensure that all artifacts are properly deployed
* call the vote
* Update to next version, e.g. {{mvn tycho-versions:set-version -DnewVersion=1.0.3-SNAPSHOT}}

> Document and further automate the IDE tooling release process
> -------------------------------------------------------------
>
>                 Key: SLING-3685
>                 URL: https://issues.apache.org/jira/browse/SLING-3685
>             Project: Sling
>          Issue Type: Task
>          Components: IDE
>            Reporter: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.2
>
>
> The current release process is very much manual, due to some of tycho's peculiarities ( see also SLING-3620 ). This task tracks the documentation of this release process and possible automation enhancements.



--
This message was sent by Atlassian JIRA
(v6.2#6252)