Skip to content

update release metadata repository url #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

update release metadata repository url #212

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions HOWTO-publish-a-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ programs in you `$PATH`:

You must have access to the following repositories:

- `git@github.openssl.org:omc/data.git`
- `git@github.com:openssl/security-advisories.git`

This contains files to be updated as part of any release.

Expand Down Expand Up @@ -148,7 +148,7 @@ In both tools, you will need to make a title and a short description.
For the title, use something like "OpenSSL 3.1.0".

For the release notes [^1], we currently use the same text as is added in the
`newsflash.txt` file to announce the release
`newsflash.md` file to announce the release
(see [Update the release data locally](#update-the-release-data-locally) below)

[^1]: The release notes field has previously been described as "description"
Expand Down Expand Up @@ -199,7 +199,7 @@ data repo*

- Newsflash *[only for public releases]*

Update the newsflash.txt file. This normally is one or two lines. Just
Update the newsflash.md file. This normally is one or two lines. Just
copy and paste existing announcements making minor changes for the date
and version number as necessary. If there is an advisory then ensure
you include a link to it.
Expand All @@ -211,7 +211,7 @@ data repo*
If there is a Security Advisory then copy it into the secadv directory.

Make a pull request from your changes, against the release metadata repo
(the release metadata repo being `git@github.openssl.org:omc/data.git`).
(the release metadata repo being `git@github.com:openssl/security-advisories.git`).
Await approval from reviewers, then merge the pull request.

# Post-publishing tasks
Expand Down