You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tooling.apache.org by wa...@apache.org on 2026/09/18 20:11:51 UTC
(tooling-trusted-releases) branch main updated: Add getting started docs
This is an automated email from the ASF dual-hosted git repository.
dave2wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
The following commit(s) were added to refs/heads/main by this push:
new 3ba11e78 Add getting started docs
3ba11e78 is described below
commit 3ba11e783d6b41e7ea48eeab9f042bed0d562ff9
Author: Dave Fisher <da...@comcast.net>
AuthorDate: Fri Sep 18 13:11:38 2026 -0700
Add getting started docs
---
atr/docs/getting-started.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/atr/docs/getting-started.md b/atr/docs/getting-started.md
index 49ba5b9a..a01ac300 100644
--- a/atr/docs/getting-started.md
+++ b/atr/docs/getting-started.md
@@ -11,3 +11,24 @@
* [Getting started with ATR](#getting-started-with-atr)
## Getting started with ATR
+
+There are prepatory steps you need to consider prior to starting your first ATR release as a Release Manager.
+If your PMC is new to using ATR you will want to make sure that the project you are releasing a new version for is properly configured.
+In ATR you move your release candidate's artifacts into the system using one or more of several methods while traditionally you would commit
+them to `svn:dist:dev`.
+
+1. ATR uses the ASF's MFA at mfa.apache.org. Make sure that you are registered first.
+2. If you are a Release Manager who is not a PMC member then you will need a PMC member to "designate" you as one from the Committee page.
+ This is a change from legacy policy.
+3. You need to make sure that ATR has your [OpenPGP public key](/keys) is linked to your PMC. If your key is already in your project's
+ `KEYS` file on `svn:dist:release` then you are ready. If not then ATR allows you to manage your [OpenPGP public keys](/keys).
+4. Depending on how you choose to upload your release candidate artifacts you may need to create a [Parsonal Access Token](/tokens) or
+ upload a [public `SSH` key](/keys).
+5. Check your PMC's [release catalog](https://release-catalog.apache.org) to assure that the list of projects is correct. Reach out to the
+ tooling team to work on any corrections.
+6. When you login to ATR your [home page](/) shows you a list of your projects as an index and scroll down to
+ * Check the project's configuration through the "About this project" link.
+ * See any release candidates that are in process.
+ * Start a new release candidate.
+ * See any finished releases including current and archived made through ATR and also as found on https://downloads.apache.org/ and
+ https://archive.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@tooling.apache.org
For additional commands, e-mail: commits-help@tooling.apache.org