diff options
| author | Brian C. Lane <bcl@redhat.com> | 2019-08-14 12:25:02 -0700 |
|---|---|---|
| committer | Brian C. Lane <bcl@redhat.com> | 2019-08-21 10:49:28 -0700 |
| commit | b0b97604d91b5b767799a645285e756eb3281989 (patch) | |
| tree | 6052c059978aecc3a92f1eae0caa1e5eebf62037 /README-release | |
| parent | ee24bd8d603f3ffbbad0abf3f55bc3a8dd6d0625 (diff) | |
| download | parted-b0b97604d91b5b767799a645285e756eb3281989.tar.gz | |
README-release: Add link to upload registration page
Without this you cannot use gnupload to send the new release tarball to
the ftp servers.
Diffstat (limited to 'README-release')
| -rw-r--r-- | README-release | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/README-release b/README-release index 78f6677..1bc525d 100644 --- a/README-release +++ b/README-release @@ -123,6 +123,13 @@ Here are most of the steps we (maintainers) follow when making a release. Once all the builds and tests have passed, +* If this is your first time creating a release you will need to have your gpg + key added to the ftp system. Read this page + + https://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html + + for the details of how to request this. + * Run the gnupload command that was suggested by your "make stable" run above. * Wait a few minutes (maybe up to 30?) and then use the release URLs to |