These instructions coemplement complement those from http://sling.apache.org/documentation/development/release-management.html, which are geared more towards bundle releases, while releasing the Launchpad is a bit more involved.
...
Since the Launchpad is a collection of bundles, it is required for each bundle included it in to be a release, rather than a SNAPSHOT. We currently have only releases in the starter, so this should not be an issue.
It is not recommended to group the Sling Starter and other bundles in the same release vote. The Sling Docker images are automatically built on DockerHub when a release tag is created and it a bundle is missing since it is not yet released the build will fail and will need to be manually recovered. It is possible to trigger a new build later on by deleting the release tag and creating it again but it complicates the release process and is therefore not recommended.
Create a new and noteworthy page
...
- https://sling.apache.org/news/sling-launchpad-8-released.html .
- https://sling.apache.org/news/sling-launchpad-9-released.html
- https://sling.apache.org/news/sling-10-released.html
- https://sling.apache.org/news/sling-11-released.html
- https://sling.apache.org/news/sling-12-released.html
Update and release the "core" set of artifacts
...
Currently we release the following artifacts (TBD):
- Sling StarterSling Launchpad Testing
- Sling Launchpad Testing WAR
- Sling Launchpad Integration TestsSling Launchpad Test Services
- Sling Launchpad Test Services WAR
- Sling Launchpad Test Fragment
- Sling Launchpad Test Bundles
- Starter Content (needs to be updated to point to API docs for the new Starter release)
- Project Archetype (needs to be updated to reference the new Starter release)
- Archetype Parent (only if needed for other archetype versions)
- Bundle Archetype (only if not working with the new Starter release)
- JCRInstall Bundle Archetype (only if not working with the new Starter release)
- Initial Content Archetype
- Slingstart Archetype
- (only if not working with the new Starter release)
The diagram below shows the projects that were released for Sling 11 and their dependencies. Some unrelated dependencies (blue) were also released as they were used as snapshots. Only one archetype (magenta) was released as the others did not need any changes.
...
Since the Sling 8 release we also provide a docker image. The Dockerfile can be found in the sling-org-apache-sling-starter-docker repo. Images are deployed by tagging the repository with the version of Sling they correspond to, for instance:
Code Block | ||
---|---|---|
| ||
git tag -a 11
git push --tags |
After the tags are pushed the DockerHub build can be triggered. We since we trigger builds based on Github tags, the type of build we use is source_type: Tag . For more details , see the /repos/private/pmc/sling
SVN repository. The build status for ongoing builds can be verified at https://hub.docker.com/r/apache/sling/builds/ .
. As of the Sling Starter 12 release, the process is automated using DockerHub automated builds . Pushing a tag of the form org.apache.sling.starter-$VERSION
will result in a DockerHub tag of $VERSION
and also in the latest
tag being updated.
There is no direct access to the DockerHub UI. If needed, a set of credentials that can be used to trigger builds are stored in the private Sling PMC area in SVN.
The automated builds setup was configured in
Jira | ||||||
---|---|---|---|---|---|---|
|
Note that, like for any Apache artifacts, the sling-org-apache-sling-starter-docker
module must be released before deploying binaries (like the Docker image) to public places.
Update local references to the old starter
...
Clean up starter documentation
The latest version of the Sling Starter is defined in the Sling site by the sling_releaseVersion
variable in src/main/jbake/templates/includes/U.groovy
. Once changed, it i recommended to verify it is used, in case usage patterns have changed from the previous version.
Update the Apache Sling Wikipedia page
The page is There may be references to old features of the starter at https://slingen.apachewikipedia.org/documentation/the-sling-engine/the-sling-launchpad.html, so make sure that this is up to wiki/Apache_Sling and we should update at least the latest released version and the corresponding release date.
Announce release
Send an email to users@sling.apache.org and announce@apache.org . For some examplesexample, see [ANN] New Release of Apache Sling 6 and [ANN] Apache Sling version 8 12 released .
See also
- Launchpad 8 release tracking task:
Jira server ASF JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SLING-5095 - dev@sling.apache.org: Sling 8 release checklist
- dev@sling.apache.org: Launchpad 7 release?
- Towards Sling 6
- dev@sling.apache.org: Sling 6 release plan
...