| commit | f1a1f12195d8538338d000dba71fb2e98de0afbb | [log] [tgz] |
|---|---|---|
| author | Surinder Singh <sursingh@gmail.com> | Mon Apr 12 12:42:16 2021 -0700 |
| committer | GitHub <noreply@github.com> | Mon Apr 12 12:42:16 2021 -0700 |
| tree | 8cc6affa28546aab7df8c31cca5500f88fbc9549 | |
| parent | 2dd4afecdf0a518e417c4eea695dbf8a2e7c9a16 [diff] |
staging and setting up vote for release candidates (#2681) This change automates staging of release candidate. The artifacts are staged to SVN and nexus repositories. This change uses https://github.com/vlsi/vlsi-release-plugins/blob/master/plugins/stage-vote-release-plugin/README.md. Preparing release candidate: 1. Checkout release branch: `git checkout -b branch-4.14 origin/branch-4.14` 2. Update the version in version.gradle and commit the change 3. Create and stage release candidate. This will build and upload all release artifacts to staging areas under nexus and SVN repos. A template for Vote email will also be generated. Link to the release notes will need to be updated in the email template. A release candidate tag will also be added. ``` ./gradlew prepareVote -Pasf -Prc=1 ``` 4. If needed additional release candidates can be create by running the above command with appropriate `rc` value 5. Once the voting is done, the release can be published using: ``` ./gradlew publishDist -Pasf -Prc=1 ``` 6. Remove stale artifacts: ``` ./gradlew removeStaleArtifacts -Pasf ``` Configuration: * Following configuration can be added to $HOME/.gradle/gradle.properties. ``` signing.gnupg.keyName=... asfCommitterId=... asfNexusUsername=... asfNexusPassword=... asfGitSourceUsername=... asfGitSourcePassword=... asfGitSitePreviewUsername=... asfGitSitePreviewPassword=... asfSvnUsername=... asfSvnPassword=... ``` * The above config can also be passed from commandline `-P<property>=<value>` Testing: The change was testing useing a local setup based on https://github.com/vlsi/asflike-release-environment Co-authored-by: Surinder Singh <surinders@splunk.com> Co-authored-by: Matteo Merli <mmerli@apache.org>
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.