You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MAINTAINERS.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COU
58
58
59
59
# Tier 3 Release Guidelines
60
60
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.
62
62
63
63
## Table of Contents
64
64
@@ -78,7 +78,7 @@ codejson-generator will see regular updates and new releases. This document desc
78
78
79
79
## Versioning
80
80
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`.
82
82
83
83
Given a version number in the `MAJOR.MINOR.PATCH` (eg., `X.Y.Z`) format, here are the differences in these terms:
84
84
@@ -145,7 +145,7 @@ Once an item is moved out of beta, close its Issue and change the text to say 'B
145
145
146
146
## Preparing a Release Candidate
147
147
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`.
149
149
150
150
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`:
151
151
@@ -199,7 +199,7 @@ Repeat as-needed for subsequent Release Candidates. Note the release branch will
199
199
200
200
## Making a Release
201
201
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:
203
203
204
204
1.**Approved**. Ensure review has been completed and approval granted.
205
205
@@ -277,4 +277,4 @@ In rare cases, a hotfix for a prior release may be required out-of-phase with th
0 commit comments