Skip to content
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.

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

Document tag-naming convention for components in sd-builder repo #71

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rocodes
Copy link
Contributor

@rocodes rocodes commented May 30, 2023

@rocodes rocodes requested review from legoktm and a team May 30, 2023 00:07
@rocodes rocodes force-pushed the component-tags-in-sd-builder branch from 1f0b5de to a4f385d Compare May 30, 2023 00:07
@@ -30,7 +30,9 @@ Step 1: Create a release candidate (rc) tag

1. Create a release branch in the repo of the component you want to release.
2. Push a changelog commit.
3. Push an rc tag in the format ``<major>.<minor>.<patch>~rcN`` on your new commit. We will be building from this tag in the next step.
3. Push an rc tag on your new commit. For components in the ``securedrop-builder`` repo, use the tag format
``securedrop-<component>-<major>.<minor>.<patch>-rcN``; for components outside this repo (i.e. ``securedrop-client``),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the very pedantic suggestion:

Suggested change
``securedrop-<component>-<major>.<minor>.<patch>-rcN``; for components outside this repo (i.e. ``securedrop-client``),
``securedrop-<component>-<major>.<minor>.<patch>-rcN``; for components outside this repo (e.g. ``securedrop-client``),

As an aside, I always considered the component name to be e.g. "securedrop-keyring", not "keyring". But writing it this way make it very clear that the "securedrop-" prefix should be included 👍🏾

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants