2. Getting started
Up: Documentation
Prev: 1. Scope
Next: 2.1. Moving from the current process
Pages:
Sections:
Getting started with ATR
There are some preparatory steps to take before you start 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.
Traditionally you would commit your release candidate's artifacts to svn:dist:dev, whereas in ATR you move them into the system using
one or more of several methods.
- ATR uses the ASF's multi-factor authentication at mfa.apache.org. Make sure that you are registered first.
- 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.
- Make sure that ATR has your OpenPGP public key linked to your PMC. If your key is already in your project's
KEYSfile onsvn:dist:releasethen you are ready. If not then ATR allows you to manage your OpenPGP public keys. - Depending on how you choose to upload your release candidate artifacts you may need to create a Personal Access Token or
upload a public
SSHkey. - Check your PMC's release catalog to make sure that the list of projects is correct. Reach out to the tooling team to work on any corrections.
- When you log in to ATR your home page shows an index of your projects. Scroll down to a project to:
- Check the project's configuration through the "About this project" link.
- See any release candidates that are in progress.
- Start a new release candidate.
- See any finished releases, current and archived, whether made through ATR or found on https://downloads.apache.org/ and https://archive.apache.org/
If your PMC is coming from the svn:dist:dev process, also read Moving from the current process, which covers
what changes and what to check before your first release.
If your project is a podling, also read Podling releases, which covers what differs for a project in the Incubator.