Skip to content

Commit bc59c66

Browse files
Update MAINTAINERS.md with project name
Signed-off-by: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
1 parent b74354c commit bc59c66

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

MAINTAINERS.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COU
5858

5959
# Tier 3 Release Guidelines
6060

61-
codejson-generator will see regular updates and new releases. This document describes the general guidelines around how and when a new release is cut.
61+
unsdg-formsite will see regular updates and new releases. This document describes the general guidelines around how and when a new release is cut.
6262

6363
## Table of Contents
6464

@@ -78,7 +78,7 @@ codejson-generator will see regular updates and new releases. This document desc
7878

7979
## Versioning
8080

81-
codejson-generator uses [Semantic Versioning](https://semver.org/). Each release is associated with a [`git tag`](github.com/DSACMS/codejson-generator/tags) of the form `X.Y.Z`.
81+
unsdg-formsite uses [Semantic Versioning](https://semver.org/). Each release is associated with a [`git tag`](github.com/CHAOSS/unsdg-formsite/tags) of the form `X.Y.Z`.
8282

8383
Given a version number in the `MAJOR.MINOR.PATCH` (eg., `X.Y.Z`) format, here are the differences in these terms:
8484

@@ -145,7 +145,7 @@ Once an item is moved out of beta, close its Issue and change the text to say 'B
145145

146146
## Preparing a Release Candidate
147147

148-
The following steps outline the process to prepare a Release Candidate of codejson-generator. This process makes public the intention and contents of an upcoming release, while allowing work on the next release to continue as usual in `dev`.
148+
The following steps outline the process to prepare a Release Candidate of unsdg-formsite. This process makes public the intention and contents of an upcoming release, while allowing work on the next release to continue as usual in `dev`.
149149

150150
1. Create a _Release branch_ from the tip of `dev` named `release-x.y.z`, where `x.y.z` is the intended version of the release. This branch will be used to prepare the Release Candidate. For example, to prepare a Release Candidate for `0.5.0`:
151151

@@ -199,7 +199,7 @@ Repeat as-needed for subsequent Release Candidates. Note the release branch will
199199

200200
## Making a Release
201201

202-
The following steps describe how to make an approved [Release Candidate](#preparing-a-release-candidate) an official release of codejson-generator:
202+
The following steps describe how to make an approved [Release Candidate](#preparing-a-release-candidate) an official release of unsdg-formsite:
203203

204204
1. **Approved**. Ensure review has been completed and approval granted.
205205

@@ -277,4 +277,4 @@ In rare cases, a hotfix for a prior release may be required out-of-phase with th
277277
This is a pre-release: DO NOT check
278278
```
279279

280-
[proj-releases-new]: https://github.com/DSACMS/codejson-generator/releases/new
280+
[proj-releases-new]: https://github.com/CHAOSS/unsdg-formsite/releases/new

0 commit comments

Comments
 (0)