Amdatu Release Procedure
Â
This release procedure is inspired by the release procedure used in the Apache community. We've modified and simplified a couple of steps to make the procedure a better fit to our own needs.
Definition of a release
Releases in Amdatu are primarily source-based releases, optionally accompanied by binaries for convenience. By definition, a source-based release is an archive containing all sources that are subject to the release and necessary build scripts to recreate the release binaries from those sources. Optionally, the archive may contain all build-time dependencies for convenience if those dependencies are not readily available elsewhere. For example, libraries that are embedded may be made part of a source-release.Â
Each release has a unique version, regardless of the outcome of the vote. This implies that version used for releases are not to be reused. This eases the communication surrounding releases and simplifies the traceability of releases. By convention, a release version is defined as "r<N>
", where <N> is a positive integer number starting at 1 and is incremented upon each release.
To verify the integrity of release artifacts SHA-256/512 checksum files must be provided for at least the source-based release as well as the R5-OBR repository file. For the binary artifacts, the R5-OBR repository file already includes proper SHA checksums, eliminating the need for external checksum files.
All released artifacts of any Amdatu project are placed in a public release repository that is accessible by Bnd(tools), that is, a R5-based OBR.
When voting on a new release of a Amdatu project, the release-candidate artifacts are placed in a (temporary) staging repository for others to verify and test. After a successful vote, the artifacts from the staging repository are moved to release repositories. When a vote is cancelled or not successful, the staging artifacts must be removed from the staging repository.
Preliminary steps
Before a release can be started, ensure that:
- all developers on the project have consensus that a release is to be made, please send a message to the mailing list (dev@lists.amdatu.org) requesting whether there are any known issues that need to be addressed or whether there is someone who is currently working on something that should be included;
- all code compiles (inside and outside an IDE) and all tests run successfully;
- verify that all external dependencies are released, or are embedded inside (to be) released artifacts. We cannot release anything that is depending on something that is still subject to change and may break a release in the future;
- verify that everything builds against specific versions, or at least bound version ranges. Do not release anything that builds against "latest" or open version ranges as it might break when newer versions of those dependencies are released;
- the versions of the to-be-released bundles are properly bumped, for example, by releasing them with Bndtools to the local release repository of the project (which uses baselining internally to determine the proper next version);
Check the packageinfo files after doing this, they sometimes revert to version 1.0.0! - all sources have the correct license headers and copyright attributions, which can be found here;
- a short "README" file in MarkDown (ReadMe.md) is available that provides pointers on how to get started; please use this template.
- License and Notice files which are correct and up to date are included in the project. The License file can be found here, please use this template for the Notice file;
- a wiki entry exists for the project to provide a place for development discussions on the project. Please use this template to create a wiki entry when none exists prior to the release to be made.
If the release includes fixes reported by JIRA issues, make sure that all those JIRA issues have their "Fix Version(s)" field filled. By convention, this should be the "next" version, which is to be renamed once the release is promoted successfully. Tagging JIRA issues with a fix version allows you to easily create filters that can be used to summarise changes in a release.
Release procedure
To automate the release procedure, a Gradle plugin has been created that provides you three additional tasks in your Gradle build.
The stageRelease
task creates and stages all artifacts to the Amdatu Repository in such way that a vote can be started (a mail template can be found below). Votes are open for at least 72 hours. Depending on the outcome of the vote, you can either use cancelRelease
to cancel the release in case the vote failed, or promoteRelease
in case the vote was successful. The results of a vote must always be communicated to the mailing lists (see below for templates)!
After a successful vote, rename the "next" release in JIRA to "r<N>" to reflect the just released version and mark it as released. Afterwards, create a new release named "next" in JIRA as preparation for the upcoming release.
Email templates
For convenience, the following email templates can be used in the various stages of a release. Be sure to replace all placeholders!
To: "Amdatu Developers List" <dev@lists.amdatu.org>
Subject: [VOTE] Release Amdatu <project> v<X>Â
Hi all,
We would like to start a vote to release Amdatu <project> v<X>.
This release solves the following bugs:
<list of bugs>
In addition, the following improvements were made:
<list of improvements>
To test and verify the staged (binary) release artifacts, you can add the
following staging repository to your "repositories.bnd" file:
aQute.bnd.deployer.repository.FixedIndexedRepo;name=Amdatu <project> Staging;locations=http://repository.amdatu.org/staging/amdatu-<project>-r<X>/index.xml.gz
If you want to verify this release by its sources, you can extract the
files from http://repository.amdatu.org/staging/amdatu-<project>-rX/amdatu-<project>-src-r<X>.tgz
and build the project from scratch.Â
Please vote to approve or disapprove the release:
[ ] +1 Approve the release;
[ ] -1 Veto the release (please provide specific comments).
The vote will be open for at least 72 hours.
-Â The Amdatu team
To: "Amdatu Developers List" <dev@lists.amdatu.org>
Subject: [CANCEL] [VOTE] Release Amdatu <project> v<X>
Hi all,
The vote on Amdatu <project> v<X>
is cancelled due to the following reasons:
<reason(s)>.
We will start a new vote once all issues are resolved.
-Â The Amdatu team
To: "Amdatu Developers List" <dev@lists.amdatu.org>
Subject: [RESULT] [VOTE] Release Amdatu <project> v<X>
Hi all,
The vote on releasing Amdatu <project> v<X> has ended with the following results:
+1: <names>;
-1:Â <names>.
The staged artifacts will be promoted to the main Amdatu Repository making them
accessible for all users.Â
Thanks for voting.
-Â The Amdatu team
To: "Amdatu Users List" <users@lists.amdatu.org>
Cc: "Amdatu Developers List" <dev@lists.amdatu.org>
Subject: [ANN] Amdatu <project> v<X> released
Hi all,
We are pleased to announce the release of Amdatu <project> v<X>!
<short description of changes/improvements>
For more information on how to use Amdatu <project>, see <url to wiki/docs>.
The released binaries are available in the Amdatu Repository.
See [1] on how to use/access them.
Enjoy!
- The Amdatu team
Â
1. https://bitbucket.org/amdatu/amdatu-repository
Appendices
Source Code License Header
/* * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */
ReadMe Template
# Amdatu ${ProjectName} Amdatu ${ProjectName} decription in a few lines ## Usage Please visit the [$ProjectName](http://www.amdatu.org/components/${componentPage}.html) component page on the Amdatu website for a detailed description on how to use the Amdatu ${ProjectName} components. ## Building The source code can be built on the command line using Gradle, or by using [Bndtools](http://bndtools.org/) in Eclipse. Tests can be ran from command line using Gradle as well, or by using JUnit in Eclipse. ### Eclipse using Bndtools When Bndtools is correctly installed in Eclipse, import all subprojects into the workspace using `Import -> Existing Projects into Workspace` from the Eclipse context menu. Ensure `project -> Build Automatically` is checked in the top menu, and when no (compilation) errors are present, each subproject's bundles should be available in their `generated` folder. ###Gradle When building from command line, invoke `./gradlew jar` from the root of the project. This will assemble all project bundles and place them in the `generated` folder of each subproject. ## Testing ### Eclipse using Bndtools Unit tests can be ran per project or per class, using JUnit in Eclipse. Unit tests are ran by right clicking a project which contains a non-empty test folder or a test class and choosing `Run As -> JUnit Test`. Integration tests can be ran in a similar way; right click an integration test project (commonly suffixed by .itest), but select `Run As -> Bnd OSGi Test Launcher (JUnit)` instead. ### Gradle Unit tests are ran by invoking `./gradlew test` from the root of the project. Integration tests can be ran by running a full build, this is done by invoking `./gradlew build` from the root of the project. More info on available Gradle tasks can be found by invoking `./gradlew tasks`. ## Gradle license plugin This project contains a Gradle license plugin which checks if all source files contain the correct license. It does so automatically when running a Gradle build from the commandline. This plugin can also be used to add missing headers to source files by running `./gradlew licenseFormat` from the root of the project. Please not though: when a different header is already present in a source file, the correct header as defined in the `etc` folder will be prefixed to the file with the already existing header, resulting in two headers! Please keep this in mind, and verify the output before committing after running this task. ## Links * [Amdatu Website](http://amdatu.org/components/${componentPage}.html); * [Source Code](https://bitbucket.org/amdatu/${componentRepo}); * [Issue Tracking](https://amdatu.atlassian.net/browse/${componentJira}); * [Development Wiki](https://amdatu.atlassian.net/wiki/display/AMDATUDEV/${componentWiki}); * [Continuous Build](https://amdatu.atlassian.net/builds/browse/${componentCIBuild}). ## License The Amdatu ${projectname} project is licensed under [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
License File
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Notice File
Amdatu ${projectName} Copyright (c) 2010-${year} - The Amdatu Foundation. This product includes software developed at The Amdatu Foundation (http://www.amdatu.org/). Licensed under the Apache License 2.0.