[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 7/29/14 11:27 AM:
--
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}}
* update the version of the source-bundle project to 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}}
* build the project with p2/gpg signing enabled {{mvn clean package -Psign}}
* build the source bundle from the source-bundle directory {{ mvn clean
package}}
* copy the following artifacts to
https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.0.2
** source bundle ( sling-ide-tooling-1.0.2.jar )
** zipped p2 repository ( org.apache.sling.ide.p2update-1.0.2.zip )
** ensure the artifacts are checksummed and gpg-signed
* 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
* upload the source bundle to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* update
https://dist.apache.org/repos/dist/release/sling/eclipse/composite\{Content,Artifacts\}.xml
to point to the latest $VERSION ( remove old one )
* archive the old artifact versions but leave pointers to archive.apache.org,
using compositeArtifacts.xml/compositeContent.xml , with a single child entry
pointing to https://archive.apache.org/dist/sling/eclipse/1.0.0/
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}}
* update the version of the source-bundle project to 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}}
* build the project with p2/gpg signing enabled {{mvn clean package -Psign}}
* build the source bundle from the source-bundle directory {{ mvn clean
package}}
* copy the following artifacts to
https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.0.2
** source bundle ( sling-ide-tooling-1.0.2.jar )
** zipped p2 repository ( org.apache.sling.ide.p2update-1.0.2.zip )
** ensure the artifacts are checksummed and gpg-signed
* 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
* upload the source bundle to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* 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
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.4
Attachments: sign.sh
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 7/22/14 12:58 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}}
* update the version of the source-bundle project to 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}}
* build the project with p2/gpg signing enabled {{mvn clean package -Psign}}
* build the source bundle from the source-bundle directory {{ mvn clean
package}}
* copy the following artifacts to
https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.0.2
** source bundle ( sling-ide-tooling-1.0.2.jar )
** zipped p2 repository ( org.apache.sling.ide.p2update-1.0.2.zip )
** ensure the artifacts are checksummed and gpg-signed
* 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
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* 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}}
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
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* 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
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
Attachments: sign.sh
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 7/7/14 8:50 AM:
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
** create GPG signatures and checksums for all uploaded jars, possibly using
the attached [^sign.sh] script
* 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}}
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
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
Attachments: sign.sh
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 7/1/14 2:44 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}}
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
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/30/14 1:56 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}}
* build 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}}
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.0}}
* build 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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/30/14 1:56 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.0}}
* build 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}}
was (Author: rombert):
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* 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.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload the src zip file with checksums and signatures for testing on the
dist/dev tree ( see https://www.apache.org/dev/release.html#host-rc ).
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files from dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
* if the vote is not successful
** remove the files from dist/dev
** remove the tag from SVN
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/30/14 1:58 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}}
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}}
* build 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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/26/14 8:25 AM:
-
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* 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.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
was (Author: rombert):
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* 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.0}}
* build the file with p2 signing enabled {{mvn clean install -Psign}}
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
** the build might fail ... but it's only required for the reactor to be built
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
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)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/26/14 8:26 AM:
-
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* 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.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload the src zip file with checksums and signatures for testing on the
dist/dev tree ( see https://www.apache.org/dev/release.html#host-rc ).
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files from dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
* if the vote is not successful
** remove the files from dist/dev
** remove the tag from SVN
was (Author: rombert):
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* 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.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
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)
