Robert Munteanu created SLING-12951:
---------------------------------------
Summary: Simplify steps for promoting IDE Tooling releases
Key: SLING-12951
URL: https://issues.apache.org/jira/browse/SLING-12951
Project: Sling
Issue Type: Improvement
Components: Build and Source Control, IDE
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.3.2
Preparing the release for the Sling IDE Tooling was reasonably automated
SLING-8307. The promotion is still a bit manual and can be improved. From
[https://sling.apache.org/documentation/development/release-management.html#releasing-the-sling-ide-tooling-1]
the following steps can be automated, taking the staging repository as input
* upload _p2update.zip_ (with signatures and checksums) to
https://dist.apache.org/repos/dist/release/sling
* upload unzipped update site to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.3.0
* upload the source bundle to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.3.0
* update
https://dist.apache.org/repos/dist/release/sling/eclipse/composite\{Content,Artifacts}.xml
to point version 1.3.0 instead of 1.2.2
## The timestamps in the composite xml files should be refreshed to "now", for
instance by using the value of {{echo "`date +%s`000"}}
* remove the old update site from
https://dist.apache.org/repos/dist/release/sling/eclipse/1.2.2/ 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.2.2/
* remove the staged artifacts from
[https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.3.0]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
