A branch named "master" MUST exist and it MUST be referred to as the
+
2.1.A branch named "master" MUST exist and it MUST be referred to as the
"master branch".
-
The master branch MUST always be in a non-broken state with its test
+
2.2.The master branch MUST always be in a non-broken state with its test
suite passing.
-
The master branch IS NOT guaranteed to always work in production
+
2.3.The master branch IS NOT guaranteed to always work in production
environments. Despite test suites passing it may at times contain
unfinished work. Only releases may be considered safe for production use.
-
The master branch SHOULD always be in a "as near as possibly ready for
+
2.4.The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new
release.
Each change (feature, bugfix, etc.) MUST be performed on separate
+
3.1.Each change (feature, bugfix, etc.) MUST be performed on separate
branches that SHOULD be referred to as "change branches".
-
All change branches MUST have descriptive names.
-
It is RECOMMENDED that you commit often locally, and that you try and
+
3.2.All change branches MUST have descriptive names.
+
3.3.It is RECOMMENDED that you commit often locally, and that you try and
keep the commits reasonably structured to avoid a messy and confusing git
history.
-
You SHOULD regularly push your work to the same named branch on the
+
3.4.You SHOULD regularly push your work to the same named branch on the
remote server.
-
You SHOULD create separate change branches for each distinctly different
+
3.5.You SHOULD create separate change branches for each distinctly different
change. You SHOULD NOT include multiple unrelated changes into a single
change branch.
-
When a change branch is created, the branch that it is created from
+
3.6.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target" branch, typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
3.7.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch.
-
After updating a change branch from its source branch you MUST push the
+
3.8.After updating a change branch from its source branch you MUST push the
change branch to the remote server. Due to the nature of rebasing, you
will be required to do a force push, and you MUST use the
"--force-with-lease" git push option when doing so instead of the regular
"--force".
-
If there is a truly valid technical reason to not use rebase when
+
3.9.If there is a truly valid technical reason to not use rebase when
updating change branches, then you can update change branches via merge
instead of rebase. The decision to use merge MUST only be taken after all
possible options to use rebase have been tried and failed. People not
@@ -258,170 +258,170 @@ you do decide to use merge instead of rebase, you MUST NOT use a mixture
of both methods, pick one and stick to it.
To merge a change branch into its merge target, you MUST open a "pull
+
4.1.To merge a change branch into its merge target, you MUST open a "pull
request" (or equivalent).
-
The purpose of a pull request is to allow others to review your changes
+
4.2.The purpose of a pull request is to allow others to review your changes
and give feedback. You can then fix any issues, complaints, and more that
might arise, and then let people review again.
-
Before creating a pull request, it is RECOMMENDED that you consider the
+
4.3.Before creating a pull request, it is RECOMMENDED that you consider the
state of your change branch's commit history. If it is messy and
confusing, it might be a good idea to rebase your branch with "git rebase
-i" to present a cleaner and easier to follow commit history for your
reviewers.
-
A pull request MUST only be merged when the change branch is up-to-date
+
4.4.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
4.5.To get feedback, help, or generally just discuss a change branch with
others, it is RECOMMENDED you create a pull request and discuss the
changes with others there. This leaves a clear and visible history of
how, when, and why the code looks and behaves the way it does.
A "version string" is a typically mostly numeric string that identifies a
+
5.1.A "version string" is a typically mostly numeric string that identifies a
specific version of a project. The version string itself MUST NOT have a
"v" prefix, but the version string can be displayed with a "v" prefix to
indicate it is a version that is being referred to.
-
The source of truth for a project's version MUST be a git tag with a name
+
5.2.The source of truth for a project's version MUST be a git tag with a name
based on the version string. This kind of tag MUST be referred to as a
"release tag".
-
It is OPTIONAL, but RECOMMENDED to also keep the version string
+
5.3.It is OPTIONAL, but RECOMMENDED to also keep the version string
hard-coded somewhere in the project code-base.
-
If you hard-code the version string into the code-base, it is RECOMMENDED
+
5.4.If you hard-code the version string into the code-base, it is RECOMMENDED
that you do so in a file called "VERSION" located in the root of the
project. But be mindful of the conventions of your programming language
and community when choosing if, where and how to hard-code the version
string.
-
If you are using a "VERSION" file in the root of the project, this file
+
5.5.If you are using a "VERSION" file in the root of the project, this file
MUST only contain the exact version string, meaning it MUST NOT have a
"v" prefix. For example "v2.11.4" is bad, and "2.11.4" is good.
-
It is OPTIONAL, but RECOMMENDED that that the version string follows
+
5.6.It is OPTIONAL, but RECOMMENDED that that the version string follows
Semantic Versioning (http://semver.org/).
To create a new release, you MUST create a git tag named as the exact
+
6.1.To create a new release, you MUST create a git tag named as the exact
version string of the release. This kind of tag MUST be referred to as a
"release tag".
-
The release tag name can OPTIONALLY be prefixed with "v". For example the
+
6.2.The release tag name can OPTIONALLY be prefixed with "v". For example the
tag name can be either "2.11.4" or "v2.11.4". It is however RECOMMENDED
that you do not use a "v" prefix. You MUST NOT use a mixture of "v"
prefixed and non-prefixed tags. Pick one form and stick to it.
-
If the version string is hard-coded into the code-base, you MUST create a
+
6.3.If the version string is hard-coded into the code-base, you MUST create a
"version bump" commit which changes the hard-coded version string of the
project.
-
When using version bump commits, the release tag MUST be placed on the
+
6.4.When using version bump commits, the release tag MUST be placed on the
version bump commit.
-
If you are not using a release branch, then the release tag, and if
+
6.5.If you are not using a release branch, then the release tag, and if
relevant the version bump commit, MUST be created directly on the master
branch.
-
The version bump commit SHOULD have a commit message title of "Bump
+
6.6.The version bump commit SHOULD have a commit message title of "Bump
version to VERSION". For example, if the new version string is "2.11.4",
the first line of the commit message SHOULD read: "Bump version to
2.11.4"
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
6.7.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation
+
6.8.If you use annotated release tags, the first line of the annotation
SHOULD read "Release VERSION". For example for version "2.11.4" the first
line of the tag annotation SHOULD read "Release 2.11.4". The second line
MUST be blank, and the changelog MUST start on the third line.
Any branch that has a name starting with "release-" SHOULD be referred to
+
7.1.Any branch that has a name starting with "release-" SHOULD be referred to
as a "release branch".
-
Any release branch which has a name ending with a specific version
+
7.2.Any release branch which has a name ending with a specific version
string, MUST be referred to as a "short-term release branch".
-
Use of short-term release branches are OPTIONAL, and intended to be used
+
7.3.Use of short-term release branches are OPTIONAL, and intended to be used
to create a specific versioned release.
-
A short-term release branch is RECOMMENDED if there is a lengthy
+
7.4.A short-term release branch is RECOMMENDED if there is a lengthy
pre-release verification process to avoid a code freeze on the master
branch.
-
Short-term release branches MUST have a name of "release-VERSION". For
+
7.5.Short-term release branches MUST have a name of "release-VERSION". For
example for version "2.11.4" the release branch name MUST be
"release-2.11.4".
-
When using a short-term release branch to create a release, the release
+
7.6.When using a short-term release branch to create a release, the release
tag and if used, version bump commit, MUST be placed directly on the
short-term release branch itself.
-
Only very minor changes should be performed on a short-term release
+
7.7.Only very minor changes should be performed on a short-term release
branch directly. Any larger changes SHOULD be done in the master branch,
and SHOULD be pulled into the release branch by rebasing it on top of the
master branch the same way a change branch pulls in updates from its
source branch.
-
After a release tag has been created, the release branch MUST be merged
+
7.8.After a release tag has been created, the release branch MUST be merged
back into its source branch and then deleted. Typically the source branch
will be the master branch.
Any release branch which has a name ending with a non-specific version
+
8.1.Any release branch which has a name ending with a non-specific version
string, MUST be referred to as a "long-term release branch". For example
"release-2.11" is a long-term release branch, while "release-2.11.4" is a
short-term release branch.
-
Use of long-term release branches are OPTIONAL, and intended for work on
+
8.2.Use of long-term release branches are OPTIONAL, and intended for work on
versions which are not currently part of the master branch. Typically
this is useful when you need to create a new maintenance release for a
older version.
-
A long-term release branch MUST have a name with a non-specific version
+
8.3.A long-term release branch MUST have a name with a non-specific version
number. For example a long-term release branch for creating new 2.9.x
releases MUST be named "release-2.9".
-
Long-term release branches for maintenance releases of older versions
+
8.4.Long-term release branches for maintenance releases of older versions
MUST be created from the relevant release tag. For example if the master
branch is on version 2.11.4 and there is a security fix for all 2.9.x
releases, the latest of which is "2.9.7". Create a new branch called
"release-2.9" from the "2.9.7" release tag. The security fix release will
then end up being version "2.9.8".
-
To create a new release from a long-term release branch, you MUST follow
+
8.5.To create a new release from a long-term release branch, you MUST follow
the same process as a release from the master branch, except the
long-term release branch takes the place of the master branch.
-
A long-term release branch should be treated with the same respect as the
+
8.6.A long-term release branch should be treated with the same respect as the
master branch. It is effectively the master branch for the release series
in question. Meaning it MUST always be in a non-broken state, MUST NOT be
force pushed to, etc.
You MUST NOT under any circumstances force push to the master branch or
+
9.1.You MUST NOT under any circumstances force push to the master branch or
to long-term release branches.
-
If a change branch which has been merged into the master branch is found
+
9.2.If a change branch which has been merged into the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged into master, or for any other
+
9.3.If a change branch is wrongfully merged into master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
You SHOULD never blindly commit all changes with "git commit -a". It is
+
10.2.You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -i" or "git add -p" to add individual
changes to the staging area so you are fully aware of what you are
committing.
-
You SHOULD always use "--force-with-lease" when doing a force push. The
+
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
10.5.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
10.6.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the
commits, allows one to revert a merge by reverting a single merge commit,
and creates a merge commit to mark the integration of the branch with
diff --git a/docs/spec/1.0.0-rc.1/index.html b/docs/spec/1.0.0-rc.1/index.html
index fd593d0..0187d15 100644
--- a/docs/spec/1.0.0-rc.1/index.html
+++ b/docs/spec/1.0.0-rc.1/index.html
@@ -8,7 +8,7 @@
document.documentElement.classList.add("dark");
}
})();
-
Changes MUST be performed on a separate branch that SHOULD be referred to
+
2.1.Changes MUST be performed on a separate branch that SHOULD be referred to
as a "change branch". All change branches MUST have descriptive names. It
is RECOMMENDED that you commit often locally, and you SHOULD regularly
push your work to the same named branch on the remote server.
-
When a change branch is created, the branch that it is created from
+
2.2.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target branch", typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
2.3.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch. To be clear you MUST NOT merge a source branch into a
change branch.
-
After rebasing a change branch on top of its source branch you MUST push
+
2.4.After rebasing a change branch on top of its source branch you MUST push
the change branch to the remote server. This will require you do a force
push, and you SHOULD use the "--force-with-lease" git push option.
-
To merge a change branch into its merge target branch, you MUST open a
+
2.5.To merge a change branch into its merge target branch, you MUST open a
"pull request" (or equivalent) so others can review and approve your
changes.
-
A pull request MUST only be merged when the change branch is up-to-date
+
2.6.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
2.7.To get feedback, help, or generally just discuss a change branch with
others, it is RECOMMENDED you do this by creating a pull request and
discuss the changes with others there.
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
3.4.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
3.5.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the commits,
allows one to revert a merge by reverting a single merge commit, and creates
a merge commit to mark the integration of the branch with master.
The project MUST have its version hard-coded somewhere in the
+
4.1.The project MUST have its version hard-coded somewhere in the
code-base. It is RECOMMENDED that this is done in a file called "VERSION"
located in the root of the project.
-
If you are using a "VERSION" file in the root of the project, this MUST
+
4.2.If you are using a "VERSION" file in the root of the project, this MUST
only contain the exact version string.
-
The version string SHOULD follow the Semantic Versioning
+
4.3.The version string SHOULD follow the Semantic Versioning
(http://semver.org/) format. Use of Semantic Versioning is OPTIONAL,
but the version string MUST NOT have a "v" prefix. For example "v2.11.4"
is bad, and "2.11.4" is good.
To create a new release, you MUST create a "version bump" commit directly
+
5.1.To create a new release, you MUST create a "version bump" commit directly
on the master branch which changes the hard-coded version value of the
project. The version bump commit MUST have a git tag created on it and
named as the exact version string.
-
A version bump commit MUST have a commit message title of "Bump version
+
5.2.A version bump commit MUST have a commit message title of "Bump version
to VERSION". For example, if the new version string is "2.11.4", the
first line of the commit message MUST read: "Bump version to 2.11.4"
-
The release tag on the version bump commit MUST be named exactly the same
+
5.3.The release tag on the version bump commit MUST be named exactly the same
as the version string. The tag name can OPTIONALLY be prefixed with
"v". For example the tag name can be either "2.11.4" or "v2.11.4".
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
5.4.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation MUST
+
5.5.If you use annotated release tags, the first line of the annotation MUST
read "Release VERSION". For example for version "2.11.4" the first line
of the tag annotation would read "Release 2.11.4". The second line must
be blank, and the changelog MUST start on the third line.
You MUST NOT under any circumstances force push to the master branch.
-
If a change branch which has been merged in to the master branch is found
+
6.1.You MUST NOT under any circumstances force push to the master branch.
+
6.2.If a change branch which has been merged in to the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged in to master, or for any other
+
6.3.If a change branch is wrongfully merged in to master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
Any branch that has a name starting with "stable-" SHOULD be referred to
+
7.1.Any branch that has a name starting with "stable-" SHOULD be referred to
as a "maintenance branch".
-
Maintenance branches are used for managing new releases of older
+
7.2.Maintenance branches are used for managing new releases of older
versions. Typically this is used to provide security updates for older
versions when the master branch has moved on to a point that a new
release for the old version cannot be made from the master branch.
-
A "maintenance release" is identical to a regular release, except the
+
7.3.A "maintenance release" is identical to a regular release, except the
version bump commit and the release tag are placed on the maintenance
branch instead of on the master branch.
-
A maintenance branch SHOULD follow a "stable-X.Y" naming pattern, where
+
7.4.A maintenance branch SHOULD follow a "stable-X.Y" naming pattern, where
"X" is the MAJOR version and "Y" is the minor version.
-
A maintenance branch MUST be created from the relevant release tag. For
+
7.5.A maintenance branch MUST be created from the relevant release tag. For
example if there is a security fix for all 2.9.x releases, the latest of
which is "2.9.7", we create a new branch called "stable-2.9" off of the
"2.9.7" release tag. The security fix release will then end up being
version "2.9.8".
-
When working on a maintenance release, the relevant maintenance branch
+
7.6.When working on a maintenance release, the relevant maintenance branch
MUST be thought of as the master branch for that maintenance work.
-
Changes in a maintenance branch SHOULD typically come from work being
+
7.7.Changes in a maintenance branch SHOULD typically come from work being
done against the master branch. Meaning changes SHOULD only trickle
downwards from the master branch. If a change needs to trickle back up
into the master branch, that work should have happened against the master
diff --git a/docs/spec/1.0.0-rc.2/index.html b/docs/spec/1.0.0-rc.2/index.html
index 69c9585..06a0a47 100644
--- a/docs/spec/1.0.0-rc.2/index.html
+++ b/docs/spec/1.0.0-rc.2/index.html
@@ -8,7 +8,7 @@
document.documentElement.classList.add("dark");
}
})();
-
A branch named "master" MUST exist and it MUST be referred to as the
+
1.1.A branch named "master" MUST exist and it MUST be referred to as the
"master branch".
-
The master branch MUST be considered bleeding edge.
-
The master branch MUST always be in a non-broken state with its test
+
1.2.The master branch MUST be considered bleeding edge.
+
1.3.The master branch MUST always be in a non-broken state with its test
suite passing.
-
The master branch SHOULD always be in a "as near as possibly ready for
+
1.4.The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new
release.
Each change (feature, bugfix, etc.) MUST be performed on separate
+
2.1.Each change (feature, bugfix, etc.) MUST be performed on separate
branches that SHOULD be referred to as "change branches". All change
branches MUST have descriptive names. It is RECOMMENDED that you commit
often locally, and you SHOULD regularly push your work to the same named
branch on the remote server.
-
You MUST create separate change branches for each distinctly different
+
2.2.You MUST create separate change branches for each distinctly different
change. You MUST NOT include multiple unrelated changes into a single
change branch.
-
When a change branch is created, the branch that it is created from
+
2.3.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target" branch, typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
2.4.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch.
-
After rebasing a change branch on top of its source branch you MUST push
+
2.5.After rebasing a change branch on top of its source branch you MUST push
the change branch to the remote server. This will require you to do a
force push, and you SHOULD use the "--force-with-lease" git push option.
To merge a change branch into its merge target, you MUST open a "pull
+
3.1.To merge a change branch into its merge target, you MUST open a "pull
request" (or equivalent) so others can review and approve your changes.
-
A pull request MUST only be merged when the change branch is up-to-date
+
3.2.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
3.3.To get feedback, help, or generally just discuss a change branch with
others, the RECOMMENDED way to do so is by creating a pull request and
discuss the changes with others there.
The project MUST have its version hard-coded somewhere in the
+
4.1.The project MUST have its version hard-coded somewhere in the
code-base. It is RECOMMENDED that this is done in a file called "VERSION"
located in the root of the project.
-
If you are using a "VERSION" file in the root of the project, this MUST
+
4.2.If you are using a "VERSION" file in the root of the project, this MUST
only contain the exact version string.
-
The version string SHOULD follow the Semantic Versioning
+
4.3.The version string SHOULD follow the Semantic Versioning
(http://semver.org/) format. Use of Semantic Versioning is OPTIONAL,
but the version string MUST NOT have a "v" prefix. For example "v2.11.4"
is bad, and "2.11.4" is good.
To create a new release, you MUST create a "version bump" commit which
+
5.1.To create a new release, you MUST create a "version bump" commit which
changes the hard-coded version string of the project. The version bump
commit MUST have a git tag created on it and named as the exact version
string.
-
If you are not using a release branch, then the version bump commit MUST
+
5.2.If you are not using a release branch, then the version bump commit MUST
be created directly on the master branch.
-
The version bump commit MUST have a commit message title of "Bump version
+
5.3.The version bump commit MUST have a commit message title of "Bump version
to VERSION". For example, if the new version string is "2.11.4", the
first line of the commit message MUST read: "Bump version to 2.11.4"
-
The release tag on the version bump commit MUST be named exactly the same
+
5.4.The release tag on the version bump commit MUST be named exactly the same
as the version string. The tag name can OPTIONALLY be prefixed with
"v". For example the tag name can be either "2.11.4" or "v2.11.4". You
MUST not use a mix of "v" prefixed and non-prefixed tags. Pick one form
and stick to it.
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
5.5.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation MUST
+
5.6.If you use annotated release tags, the first line of the annotation MUST
read "Release VERSION". For example for version "2.11.4" the first line
of the tag annotation would read "Release 2.11.4". The second line must
be blank, and the changelog MUST start on the third line.
6.3.Changes in a release branch SHOULD typically come from work being
done against the master branch. Meaning changes SHOULD only trickle
downwards from the master branch. If a change needs to trickle back up
into the master branch, that work should have happened against the master
branch in the first place. One exception to this is version bump commits.
-
There are two types of release branches; short-term, and long-term.
-
Short-Term Release Branches
+
6.4.There are two types of release branches; short-term, and long-term.
A short-term release branch is RECOMMENDED if there is a lengthy
+
6.5.1.Used for creating a specific versioned release.
+
6.5.2.A short-term release branch is RECOMMENDED if there is a lengthy
pre-release verification process to avoid a code freeze on the master
branch.
-
MUST have a name of "release-VERSION". For example for version
+
6.5.3.MUST have a name of "release-VERSION". For example for version
"2.11.4" the release branch name MUST be "release-2.11.4".
-
When using a short-term release branch, the version bump commit and
+
6.5.4.When using a short-term release branch, the version bump commit and
release tag MUST be made directly on the release branch itself.
-
Only very minor changes should be performed on a short-term release
+
6.5.5.Only very minor changes should be performed on a short-term release
branch directly. Any larger changes SHOULD be done in the master
branch, and SHOULD be pulled into the release branch by rebasing it
on top of the master branch the same way a change branch pulls in
updates from its source branch.
-
After the version bump commit and release tag have been created, the
+
6.5.6.After the version bump commit and release tag have been created, the
release branch MUST be merged back into its source branch and then
deleted. Typically the source branch will be the master branch.
Used for work on versions which are not currently part of the master
+
6.6.1.Used for work on versions which are not currently part of the master
branch. Typically this is useful when you need to create a new
maintenance release for a older version.
-
The branch name MUST have a non-specific version number. For example
+
6.6.2.The branch name MUST have a non-specific version number. For example
a long-term release branch for creating new 2.9.x releases would be
named "release-2.9".
-
To create a new release from a long-term release branch, you MUST
+
6.6.3.To create a new release from a long-term release branch, you MUST
create a version bump commit and release tag directly on the release
branch.
-
A long-term release branch MUST be created from the relevant release
+
6.6.4.A long-term release branch MUST be created from the relevant release
tag. For example if the master branch is on version 2.11.4 and there
is a security fix for all 2.9.x releases, the latest of which is
"2.9.7". Create a new branch called "release-2.9" off of the "2.9.7"
@@ -330,38 +330,38 @@ release tag. The security fix release will then end up being version
You MUST NOT under any circumstances force push to the master branch.
-
If a change branch which has been merged into the master branch is found
+
7.1.You MUST NOT under any circumstances force push to the master branch.
+
7.2.If a change branch which has been merged into the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged into master, or for any other
+
7.3.If a change branch is wrongfully merged into master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
You SHOULD never blindly commit all changes with "git commit -a". It is
+
8.2.You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -i" to add individual changes to the staging
area so you are fully aware of what you are committing.
-
You SHOULD always use "--force-with-lease" when doing a force push. The
+
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
8.5.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
8.6.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the
commits, allows one to revert a merge by reverting a single merge commit,
and creates a merge commit to mark the integration of the branch with
diff --git a/docs/spec/1.0.0-rc.3/index.html b/docs/spec/1.0.0-rc.3/index.html
index a284cb0..515a233 100644
--- a/docs/spec/1.0.0-rc.3/index.html
+++ b/docs/spec/1.0.0-rc.3/index.html
@@ -8,7 +8,7 @@
document.documentElement.classList.add("dark");
}
})();
-
A branch named "master" MUST exist and it MUST be referred to as the
+
2.1.A branch named "master" MUST exist and it MUST be referred to as the
"master branch".
-
The master branch MUST always be in a non-broken state with its test
+
2.2.The master branch MUST always be in a non-broken state with its test
suite passing.
-
The master branch IS NOT guaranteed to always work in production
+
2.3.The master branch IS NOT guaranteed to always work in production
environments. Despite test suites passing it may at times contain
unfinished work. Only releases may be considered safe for production use.
-
The master branch SHOULD always be in a "as near as possibly ready for
+
2.4.The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new
release.
Each change (feature, bugfix, etc.) MUST be performed on separate
+
3.1.Each change (feature, bugfix, etc.) MUST be performed on separate
branches that SHOULD be referred to as "change branches". All change
branches MUST have descriptive names. It is RECOMMENDED that you commit
often locally, and you SHOULD regularly push your work to the same named
branch on the remote server.
-
You MUST create separate change branches for each distinctly different
+
3.2.You MUST create separate change branches for each distinctly different
change. You MUST NOT include multiple unrelated changes into a single
change branch.
-
When a change branch is created, the branch that it is created from
+
3.3.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target" branch, typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
3.4.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch.
-
After rebasing a change branch on top of its source branch you MUST push
+
3.5.After rebasing a change branch on top of its source branch you MUST push
the change branch to the remote server. This will require you to do a
force push, and you SHOULD use the "--force-with-lease" git push option.
To merge a change branch into its merge target, you MUST open a "pull
+
4.1.To merge a change branch into its merge target, you MUST open a "pull
request" (or equivalent) so others can review and approve your changes.
-
A pull request MUST only be merged when the change branch is up-to-date
+
4.2.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
4.3.To get feedback, help, or generally just discuss a change branch with
others, the RECOMMENDED way to do so is by creating a pull request and
discuss the changes with others there.
The project MUST have its version hard-coded somewhere in the
+
5.1.The project MUST have its version hard-coded somewhere in the
code-base. It is RECOMMENDED that this is done in a file called "VERSION"
located in the root of the project.
-
If you are using a "VERSION" file in the root of the project, this MUST
+
5.2.If you are using a "VERSION" file in the root of the project, this MUST
only contain the exact version string.
-
The version string SHOULD follow the Semantic Versioning
+
5.3.The version string SHOULD follow the Semantic Versioning
(http://semver.org/) format. Use of Semantic Versioning is OPTIONAL,
but the version string MUST NOT have a "v" prefix. For example "v2.11.4"
is bad, and "2.11.4" is good.
To create a new release, you MUST create a "version bump" commit which
+
6.1.To create a new release, you MUST create a "version bump" commit which
changes the hard-coded version string of the project. The version bump
commit MUST have a git tag created on it and named as the exact version
string.
-
If you are not using a release branch, then the version bump commit MUST
+
6.2.If you are not using a release branch, then the version bump commit MUST
be created directly on the master branch.
-
The version bump commit MUST have a commit message title of "Bump version
+
6.3.The version bump commit MUST have a commit message title of "Bump version
to VERSION". For example, if the new version string is "2.11.4", the
first line of the commit message MUST read: "Bump version to 2.11.4"
-
The release tag on the version bump commit MUST be named exactly the same
+
6.4.The release tag on the version bump commit MUST be named exactly the same
as the version string. The tag name can OPTIONALLY be prefixed with
"v". For example the tag name can be either "2.11.4" or "v2.11.4". You
MUST not use a mix of "v" prefixed and non-prefixed tags. Pick one form
and stick to it.
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
6.5.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation MUST
+
6.6.If you use annotated release tags, the first line of the annotation MUST
read "Release VERSION". For example for version "2.11.4" the first line
of the tag annotation would read "Release 2.11.4". The second line must
be blank, and the changelog MUST start on the third line.
7.3.Changes in a release branch SHOULD typically come from work being
done against the master branch. Meaning changes SHOULD only trickle
downwards from the master branch. If a change needs to trickle back up
into the master branch, that work should have happened against the master
branch in the first place. One exception to this is version bump commits.
-
There are two types of release branches; short-term, and long-term.
-
Short-Term Release Branches
+
7.4.There are two types of release branches; short-term, and long-term.
A short-term release branch is RECOMMENDED if there is a lengthy
+
7.5.1.Used for creating a specific versioned release.
+
7.5.2.A short-term release branch is RECOMMENDED if there is a lengthy
pre-release verification process to avoid a code freeze on the master
branch.
-
MUST have a name of "release-VERSION". For example for version
+
7.5.3.MUST have a name of "release-VERSION". For example for version
"2.11.4" the release branch name MUST be "release-2.11.4".
-
When using a short-term release branch, the version bump commit and
+
7.5.4.When using a short-term release branch, the version bump commit and
release tag MUST be made directly on the release branch itself.
-
Only very minor changes should be performed on a short-term release
+
7.5.5.Only very minor changes should be performed on a short-term release
branch directly. Any larger changes SHOULD be done in the master
branch, and SHOULD be pulled into the release branch by rebasing it
on top of the master branch the same way a change branch pulls in
updates from its source branch.
-
After the version bump commit and release tag have been created, the
+
7.5.6.After the version bump commit and release tag have been created, the
release branch MUST be merged back into its source branch and then
deleted. Typically the source branch will be the master branch.
Used for work on versions which are not currently part of the master
+
7.6.1.Used for work on versions which are not currently part of the master
branch. Typically this is useful when you need to create a new
maintenance release for a older version.
-
The branch name MUST have a non-specific version number. For example
+
7.6.2.The branch name MUST have a non-specific version number. For example
a long-term release branch for creating new 2.9.x releases would be
named "release-2.9".
-
To create a new release from a long-term release branch, you MUST
+
7.6.3.To create a new release from a long-term release branch, you MUST
create a version bump commit and release tag directly on the release
branch.
-
A long-term release branch MUST be created from the relevant release
+
7.6.4.A long-term release branch MUST be created from the relevant release
tag. For example if the master branch is on version 2.11.4 and there
is a security fix for all 2.9.x releases, the latest of which is
"2.9.7". Create a new branch called "release-2.9" off of the "2.9.7"
@@ -339,38 +339,38 @@ release tag. The security fix release will then end up being version
You MUST NOT under any circumstances force push to the master branch.
-
If a change branch which has been merged into the master branch is found
+
8.1.You MUST NOT under any circumstances force push to the master branch.
+
8.2.If a change branch which has been merged into the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged into master, or for any other
+
8.3.If a change branch is wrongfully merged into master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
You SHOULD never blindly commit all changes with "git commit -a". It is
+
9.2.You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -i" to add individual changes to the staging
area so you are fully aware of what you are committing.
-
You SHOULD always use "--force-with-lease" when doing a force push. The
+
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
9.5.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
9.6.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the
commits, allows one to revert a merge by reverting a single merge commit,
and creates a merge commit to mark the integration of the branch with
diff --git a/docs/spec/1.0.0-rc.4/index.html b/docs/spec/1.0.0-rc.4/index.html
index 96fb254..4eb50e8 100644
--- a/docs/spec/1.0.0-rc.4/index.html
+++ b/docs/spec/1.0.0-rc.4/index.html
@@ -8,7 +8,7 @@
document.documentElement.classList.add("dark");
}
})();
-
A branch named "master" MUST exist and it MUST be referred to as the
+
2.1.A branch named "master" MUST exist and it MUST be referred to as the
"master branch".
-
The master branch MUST always be in a non-broken state with its test
+
2.2.The master branch MUST always be in a non-broken state with its test
suite passing.
-
The master branch IS NOT guaranteed to always work in production
+
2.3.The master branch IS NOT guaranteed to always work in production
environments. Despite test suites passing it may at times contain
unfinished work. Only releases may be considered safe for production use.
-
The master branch SHOULD always be in a "as near as possibly ready for
+
2.4.The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new
release.
Each change (feature, bugfix, etc.) MUST be performed on separate
+
3.1.Each change (feature, bugfix, etc.) MUST be performed on separate
branches that SHOULD be referred to as "change branches".
-
All change branches MUST have descriptive names.
-
It is RECOMMENDED that you commit often locally, and that you try and
+
3.2.All change branches MUST have descriptive names.
+
3.3.It is RECOMMENDED that you commit often locally, and that you try and
keep the commits reasonably structured to avoid a messy and confusing git
history.
-
You SHOULD regularly push your work to the same named branch on the
+
3.4.You SHOULD regularly push your work to the same named branch on the
remote server.
-
You SHOULD create separate change branches for each distinctly different
+
3.5.You SHOULD create separate change branches for each distinctly different
change. You SHOULD NOT include multiple unrelated changes into a single
change branch.
-
When a change branch is created, the branch that it is created from
+
3.6.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target" branch, typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
3.7.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch.
-
After updating a change branch from its source branch you MUST push the
+
3.8.After updating a change branch from its source branch you MUST push the
change branch to the remote server. Due to the nature of rebasing, you
will be required to do a force push, and you MUST use the
"--force-with-lease" git push option when doing so instead of the regular
"--force".
-
If there is a truly valid technical reason to not use rebase when
+
3.9.If there is a truly valid technical reason to not use rebase when
updating change branches, then you can update change branches via merge
instead of rebase. The decision to use merge MUST only be taken after all
possible options to use rebase have been tried and failed. People not
@@ -247,169 +247,169 @@ you do decide to use merge instead of rebase, you MUST NOT use a mixture
of both methods, pick one and stick to it.
To merge a change branch into its merge target, you MUST open a "pull
+
4.1.To merge a change branch into its merge target, you MUST open a "pull
request" (or equivalent).
-
The purpose of a pull request is to allow others to review your changes
+
4.2.The purpose of a pull request is to allow others to review your changes
and give feedback. You can then fix any issues, complaints, and more that
might arise, and then let people review again.
-
Before creating a pull request, it is RECOMMENDED that you consider the
+
4.3.Before creating a pull request, it is RECOMMENDED that you consider the
state of your change branch's commit history. If it is messy and
confusing, it might be a good idea to rebase your branch with "git rebase
-i" to present a cleaner and easier to follow commit history for your
reviewers.
-
A pull request MUST only be merged when the change branch is up-to-date
+
4.4.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
4.5.To get feedback, help, or generally just discuss a change branch with
others, the RECOMMENDED way to do so is by creating a pull request and
discuss the changes with others there.
A "version string" is a typically mostly numeric string that identifies a
+
5.1.A "version string" is a typically mostly numeric string that identifies a
specific version of a project. The version string itself MUST NOT have a
"v" prefix, but the version string can be displayed with a "v" prefix to
indicate it is a version that is being referred to.
-
The source of truth for a project's version MUST be a git tag with a name
+
5.2.The source of truth for a project's version MUST be a git tag with a name
based on the version string. This kind of tag MUST be referred to as a
"release tag".
-
It is OPTIONAL, but RECOMMENDED to also keep the version string
+
5.3.It is OPTIONAL, but RECOMMENDED to also keep the version string
hard-coded somewhere in the project code-base.
-
If you hard-code the version string into the code-base, it is RECOMMENDED
+
5.4.If you hard-code the version string into the code-base, it is RECOMMENDED
that you do so in a file called "VERSION" located in the root of the
project. But be mindful of the conventions of your programming language
and community when choosing if, where and how to hard-code the version
string.
-
If you are using a "VERSION" file in the root of the project, this file
+
5.5.If you are using a "VERSION" file in the root of the project, this file
MUST only contain the exact version string, meaning it MUST NOT have a
"v" prefix. For example "v2.11.4" is bad, and "2.11.4" is good.
-
It is OPTIONAL, but RECOMMENDED that that the version string follows
+
5.6.It is OPTIONAL, but RECOMMENDED that that the version string follows
Semantic Versioning (http://semver.org/).
To create a new release, you MUST create a git tag named as the exact
+
6.1.To create a new release, you MUST create a git tag named as the exact
version string of the release. This kind of tag MUST be referred to as a
"release tag".
-
The release tag name can OPTIONALLY be prefixed with "v". For example the
+
6.2.The release tag name can OPTIONALLY be prefixed with "v". For example the
tag name can be either "2.11.4" or "v2.11.4". It is however RECOMMENDED
that you do not use a "v" prefix. You MUST NOT use a mixture of "v"
prefixed and non-prefixed tags. Pick one form and stick to it.
-
If the version string is hard-coded into the code-base, you MUST create a
+
6.3.If the version string is hard-coded into the code-base, you MUST create a
"version bump" commit which changes the hard-coded version string of the
project.
-
When using version bump commits, the release tag MUST be placed on the
+
6.4.When using version bump commits, the release tag MUST be placed on the
version bump commit.
-
If you are not using a release branch, then the release tag, and if
+
6.5.If you are not using a release branch, then the release tag, and if
relevant the version bump commit, MUST be created directly on the master
branch.
-
The version bump commit SHOULD have a commit message title of "Bump
+
6.6.The version bump commit SHOULD have a commit message title of "Bump
version to VERSION". For example, if the new version string is "2.11.4",
the first line of the commit message SHOULD read: "Bump version to
2.11.4"
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
6.7.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation
+
6.8.If you use annotated release tags, the first line of the annotation
SHOULD read "Release VERSION". For example for version "2.11.4" the first
line of the tag annotation SHOULD read "Release 2.11.4". The second line
MUST be blank, and the changelog MUST start on the third line.
Any branch that has a name starting with "release-" SHOULD be referred to
+
7.1.Any branch that has a name starting with "release-" SHOULD be referred to
as a "release branch".
-
Any release branch which has a name ending with a specific version
+
7.2.Any release branch which has a name ending with a specific version
string, MUST be referred to as a "short-term release branch".
-
Use of short-term release branches are OPTIONAL, and intended to be used
+
7.3.Use of short-term release branches are OPTIONAL, and intended to be used
to create a specific versioned release.
-
A short-term release branch is RECOMMENDED if there is a lengthy
+
7.4.A short-term release branch is RECOMMENDED if there is a lengthy
pre-release verification process to avoid a code freeze on the master
branch.
-
Short-term release branches MUST have a name of "release-VERSION". For
+
7.5.Short-term release branches MUST have a name of "release-VERSION". For
example for version "2.11.4" the release branch name MUST be
"release-2.11.4".
-
When using a short-term release branch to create a release, the release
+
7.6.When using a short-term release branch to create a release, the release
tag and if used, version bump commit, MUST be placed directly on the
short-term release branch itself.
-
Only very minor changes should be performed on a short-term release
+
7.7.Only very minor changes should be performed on a short-term release
branch directly. Any larger changes SHOULD be done in the master branch,
and SHOULD be pulled into the release branch by rebasing it on top of the
master branch the same way a change branch pulls in updates from its
source branch.
-
After a release tag has been created, the release branch MUST be merged
+
7.8.After a release tag has been created, the release branch MUST be merged
back into its source branch and then deleted. Typically the source branch
will be the master branch.
Any release branch which has a name ending with a non-specific version
+
8.1.Any release branch which has a name ending with a non-specific version
string, MUST be referred to as a "long-term release branch". For example
"release-2.11" is a long-term release branch, while "release-2.11.4" is a
short-term release branch.
-
Use of long-term release branches are OPTIONAL, and intended for work on
+
8.2.Use of long-term release branches are OPTIONAL, and intended for work on
versions which are not currently part of the master branch. Typically
this is useful when you need to create a new maintenance release for a
older version.
-
A long-term release branch MUST have a name with a non-specific version
+
8.3.A long-term release branch MUST have a name with a non-specific version
number. For example a long-term release branch for creating new 2.9.x
releases MUST be named "release-2.9".
-
Long-term release branches for maintenance releases of older versions
+
8.4.Long-term release branches for maintenance releases of older versions
MUST be created from the relevant release tag. For example if the master
branch is on version 2.11.4 and there is a security fix for all 2.9.x
releases, the latest of which is "2.9.7". Create a new branch called
"release-2.9" off of the "2.9.7" release tag. The security fix release
will then end up being version "2.9.8".
-
To create a new release from a long-term release branch, you MUST follow
+
8.5.To create a new release from a long-term release branch, you MUST follow
the same process as a release from the master branch, except the
long-term release branch takes the place of the master branch.
-
A long-term release branch should be treated with the same respect as the
+
8.6.A long-term release branch should be treated with the same respect as the
master branch. It is effectively the master branch for the release series
in question. Meaning it MUST always be in a non-broken state, MUST NOT be
force pushed to, etc.
You MUST NOT under any circumstances force push to the master branch or
+
9.1.You MUST NOT under any circumstances force push to the master branch or
to long-term release branches.
-
If a change branch which has been merged into the master branch is found
+
9.2.If a change branch which has been merged into the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged into master, or for any other
+
9.3.If a change branch is wrongfully merged into master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
You SHOULD never blindly commit all changes with "git commit -a". It is
+
10.2.You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -i" or "git add -p" to add individual
changes to the staging area so you are fully aware of what you are
committing.
-
You SHOULD always use "--force-with-lease" when doing a force push. The
+
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
10.5.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
10.6.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the
commits, allows one to revert a merge by reverting a single merge commit,
and creates a merge commit to mark the integration of the branch with
diff --git a/docs/spec/1.0.0-rc.5/index.html b/docs/spec/1.0.0-rc.5/index.html
index 990be76..217f055 100644
--- a/docs/spec/1.0.0-rc.5/index.html
+++ b/docs/spec/1.0.0-rc.5/index.html
@@ -8,7 +8,7 @@
document.documentElement.classList.add("dark");
}
})();
-
A branch named "master" MUST exist and it MUST be referred to as the
+
2.1.A branch named "master" MUST exist and it MUST be referred to as the
"master branch".
-
The master branch MUST always be in a non-broken state with its test
+
2.2.The master branch MUST always be in a non-broken state with its test
suite passing.
-
The master branch IS NOT guaranteed to always work in production
+
2.3.The master branch IS NOT guaranteed to always work in production
environments. Despite test suites passing it may at times contain
unfinished work. Only releases may be considered safe for production use.
-
The master branch SHOULD always be in a "as near as possibly ready for
+
2.4.The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new
release.
Each change (feature, bugfix, etc.) MUST be performed on separate
+
3.1.Each change (feature, bugfix, etc.) MUST be performed on separate
branches that SHOULD be referred to as "change branches".
-
All change branches MUST have descriptive names.
-
It is RECOMMENDED that you commit often locally, and that you try and
+
3.2.All change branches MUST have descriptive names.
+
3.3.It is RECOMMENDED that you commit often locally, and that you try and
keep the commits reasonably structured to avoid a messy and confusing git
history.
-
You SHOULD regularly push your work to the same named branch on the
+
3.4.You SHOULD regularly push your work to the same named branch on the
remote server.
-
You SHOULD create separate change branches for each distinctly different
+
3.5.You SHOULD create separate change branches for each distinctly different
change. You SHOULD NOT include multiple unrelated changes into a single
change branch.
-
When a change branch is created, the branch that it is created from
+
3.6.When a change branch is created, the branch that it is created from
SHOULD be referred to as the "source branch". Each change branch also
needs a designated "merge target" branch, typically this will be the same
as the source branch.
-
Change branches MUST be regularly updated with any changes from their
+
3.7.Change branches MUST be regularly updated with any changes from their
source branch. This MUST be done by rebasing the change branch on top of
the source branch.
-
After updating a change branch from its source branch you MUST push the
+
3.8.After updating a change branch from its source branch you MUST push the
change branch to the remote server. Due to the nature of rebasing, you
will be required to do a force push, and you MUST use the
"--force-with-lease" git push option when doing so instead of the regular
"--force".
-
If there is a truly valid technical reason to not use rebase when
+
3.9.If there is a truly valid technical reason to not use rebase when
updating change branches, then you can update change branches via merge
instead of rebase. The decision to use merge MUST only be taken after all
possible options to use rebase have been tried and failed. People not
@@ -258,170 +258,170 @@ you do decide to use merge instead of rebase, you MUST NOT use a mixture
of both methods, pick one and stick to it.
To merge a change branch into its merge target, you MUST open a "pull
+
4.1.To merge a change branch into its merge target, you MUST open a "pull
request" (or equivalent).
-
The purpose of a pull request is to allow others to review your changes
+
4.2.The purpose of a pull request is to allow others to review your changes
and give feedback. You can then fix any issues, complaints, and more that
might arise, and then let people review again.
-
Before creating a pull request, it is RECOMMENDED that you consider the
+
4.3.Before creating a pull request, it is RECOMMENDED that you consider the
state of your change branch's commit history. If it is messy and
confusing, it might be a good idea to rebase your branch with "git rebase
-i" to present a cleaner and easier to follow commit history for your
reviewers.
-
A pull request MUST only be merged when the change branch is up-to-date
+
4.4.A pull request MUST only be merged when the change branch is up-to-date
with its source branch, the test suite is passing, and you and others are
happy with the change. This is especially important if the merge target
is the master branch.
-
To get feedback, help, or generally just discuss a change branch with
+
4.5.To get feedback, help, or generally just discuss a change branch with
others, it is RECOMMENDED you create a pull request and discuss the
changes with others there. This leaves a clear and visible history of
how, when, and why the code looks and behaves the way it does.
A "version string" is a typically mostly numeric string that identifies a
+
5.1.A "version string" is a typically mostly numeric string that identifies a
specific version of a project. The version string itself MUST NOT have a
"v" prefix, but the version string can be displayed with a "v" prefix to
indicate it is a version that is being referred to.
-
The source of truth for a project's version MUST be a git tag with a name
+
5.2.The source of truth for a project's version MUST be a git tag with a name
based on the version string. This kind of tag MUST be referred to as a
"release tag".
-
It is OPTIONAL, but RECOMMENDED to also keep the version string
+
5.3.It is OPTIONAL, but RECOMMENDED to also keep the version string
hard-coded somewhere in the project code-base.
-
If you hard-code the version string into the code-base, it is RECOMMENDED
+
5.4.If you hard-code the version string into the code-base, it is RECOMMENDED
that you do so in a file called "VERSION" located in the root of the
project. But be mindful of the conventions of your programming language
and community when choosing if, where and how to hard-code the version
string.
-
If you are using a "VERSION" file in the root of the project, this file
+
5.5.If you are using a "VERSION" file in the root of the project, this file
MUST only contain the exact version string, meaning it MUST NOT have a
"v" prefix. For example "v2.11.4" is bad, and "2.11.4" is good.
-
It is OPTIONAL, but RECOMMENDED that that the version string follows
+
5.6.It is OPTIONAL, but RECOMMENDED that that the version string follows
Semantic Versioning (http://semver.org/).
To create a new release, you MUST create a git tag named as the exact
+
6.1.To create a new release, you MUST create a git tag named as the exact
version string of the release. This kind of tag MUST be referred to as a
"release tag".
-
The release tag name can OPTIONALLY be prefixed with "v". For example the
+
6.2.The release tag name can OPTIONALLY be prefixed with "v". For example the
tag name can be either "2.11.4" or "v2.11.4". It is however RECOMMENDED
that you do not use a "v" prefix. You MUST NOT use a mixture of "v"
prefixed and non-prefixed tags. Pick one form and stick to it.
-
If the version string is hard-coded into the code-base, you MUST create a
+
6.3.If the version string is hard-coded into the code-base, you MUST create a
"version bump" commit which changes the hard-coded version string of the
project.
-
When using version bump commits, the release tag MUST be placed on the
+
6.4.When using version bump commits, the release tag MUST be placed on the
version bump commit.
-
If you are not using a release branch, then the release tag, and if
+
6.5.If you are not using a release branch, then the release tag, and if
relevant the version bump commit, MUST be created directly on the master
branch.
-
The version bump commit SHOULD have a commit message title of "Bump
+
6.6.The version bump commit SHOULD have a commit message title of "Bump
version to VERSION". For example, if the new version string is "2.11.4",
the first line of the commit message SHOULD read: "Bump version to
2.11.4"
-
It is RECOMMENDED that release tags are lightweight tags, but you can
+
6.7.It is RECOMMENDED that release tags are lightweight tags, but you can
OPTIONALLY use annotated tags if you want to include changelog
information in the release tag itself.
-
If you use annotated release tags, the first line of the annotation
+
6.8.If you use annotated release tags, the first line of the annotation
SHOULD read "Release VERSION". For example for version "2.11.4" the first
line of the tag annotation SHOULD read "Release 2.11.4". The second line
MUST be blank, and the changelog MUST start on the third line.
Any branch that has a name starting with "release-" SHOULD be referred to
+
7.1.Any branch that has a name starting with "release-" SHOULD be referred to
as a "release branch".
-
Any release branch which has a name ending with a specific version
+
7.2.Any release branch which has a name ending with a specific version
string, MUST be referred to as a "short-term release branch".
-
Use of short-term release branches are OPTIONAL, and intended to be used
+
7.3.Use of short-term release branches are OPTIONAL, and intended to be used
to create a specific versioned release.
-
A short-term release branch is RECOMMENDED if there is a lengthy
+
7.4.A short-term release branch is RECOMMENDED if there is a lengthy
pre-release verification process to avoid a code freeze on the master
branch.
-
Short-term release branches MUST have a name of "release-VERSION". For
+
7.5.Short-term release branches MUST have a name of "release-VERSION". For
example for version "2.11.4" the release branch name MUST be
"release-2.11.4".
-
When using a short-term release branch to create a release, the release
+
7.6.When using a short-term release branch to create a release, the release
tag and if used, version bump commit, MUST be placed directly on the
short-term release branch itself.
-
Only very minor changes should be performed on a short-term release
+
7.7.Only very minor changes should be performed on a short-term release
branch directly. Any larger changes SHOULD be done in the master branch,
and SHOULD be pulled into the release branch by rebasing it on top of the
master branch the same way a change branch pulls in updates from its
source branch.
-
After a release tag has been created, the release branch MUST be merged
+
7.8.After a release tag has been created, the release branch MUST be merged
back into its source branch and then deleted. Typically the source branch
will be the master branch.
Any release branch which has a name ending with a non-specific version
+
8.1.Any release branch which has a name ending with a non-specific version
string, MUST be referred to as a "long-term release branch". For example
"release-2.11" is a long-term release branch, while "release-2.11.4" is a
short-term release branch.
-
Use of long-term release branches are OPTIONAL, and intended for work on
+
8.2.Use of long-term release branches are OPTIONAL, and intended for work on
versions which are not currently part of the master branch. Typically
this is useful when you need to create a new maintenance release for a
older version.
-
A long-term release branch MUST have a name with a non-specific version
+
8.3.A long-term release branch MUST have a name with a non-specific version
number. For example a long-term release branch for creating new 2.9.x
releases MUST be named "release-2.9".
-
Long-term release branches for maintenance releases of older versions
+
8.4.Long-term release branches for maintenance releases of older versions
MUST be created from the relevant release tag. For example if the master
branch is on version 2.11.4 and there is a security fix for all 2.9.x
releases, the latest of which is "2.9.7". Create a new branch called
"release-2.9" from the "2.9.7" release tag. The security fix release will
then end up being version "2.9.8".
-
To create a new release from a long-term release branch, you MUST follow
+
8.5.To create a new release from a long-term release branch, you MUST follow
the same process as a release from the master branch, except the
long-term release branch takes the place of the master branch.
-
A long-term release branch should be treated with the same respect as the
+
8.6.A long-term release branch should be treated with the same respect as the
master branch. It is effectively the master branch for the release series
in question. Meaning it MUST always be in a non-broken state, MUST NOT be
force pushed to, etc.
You MUST NOT under any circumstances force push to the master branch or
+
9.1.You MUST NOT under any circumstances force push to the master branch or
to long-term release branches.
-
If a change branch which has been merged into the master branch is found
+
9.2.If a change branch which has been merged into the master branch is found
to have a bug in it, the bug fix work MUST be done as a new separate
change branch and MUST follow the same workflow as any other change
branch.
-
If a change branch is wrongfully merged into master, or for any other
+
9.3.If a change branch is wrongfully merged into master, or for any other
reason the merge must be undone, you MUST undo the merge by reverting the
merge commit itself. Effectively creating a new commit that reverses all
the relevant changes.
You SHOULD never blindly commit all changes with "git commit -a". It is
+
10.2.You SHOULD never blindly commit all changes with "git commit -a". It is
RECOMMENDED you use "git add -i" or "git add -p" to add individual
changes to the staging area so you are fully aware of what you are
committing.
-
You SHOULD always use "--force-with-lease" when doing a force push. The
+
It is RECOMMENDED that you always do "git pull --rebase" instead of "git
+
10.5.It is RECOMMENDED that you always do "git pull --rebase" instead of "git
pull" to avoid unnecessary merge commits. You can make this the default
behavior of "git pull" with "git config --global pull.rebase true".
-
It is RECOMMENDED that all branches be merged using "git merge --no-ff".
+
10.6.It is RECOMMENDED that all branches be merged using "git merge --no-ff".
This makes sure the reference to the original branch is kept in the
commits, allows one to revert a merge by reverting a single merge commit,
and creates a merge commit to mark the integration of the branch with
diff --git a/src/styles/global.css b/src/styles/global.css
index ed4dc96..93376bd 100644
--- a/src/styles/global.css
+++ b/src/styles/global.css
@@ -416,32 +416,39 @@ html {
text-align: right;
font-weight: 500;
color: theme(colors.slate.400);
+ transition: opacity 0.15s;
}
.dark .prose-spec ol>li::before {
color: theme(colors.neutral.500);
}
- /* Invisible anchor link that appears on hover */
+ /* Anchor link with clause number - hidden by default, shown on hover */
.prose-spec .clause-link {
position: absolute;
- left: -3.5rem;
- top: 0.125rem;
- width: 1.25rem;
- height: 1.25rem;
- display: flex;
- align-items: center;
- justify-content: center;
+ right: 100%;
+ margin-right: 0.5rem;
+ font-weight: 500;
+ color: theme(colors.slate.400);
+ text-decoration: none;
opacity: 0;
transition: opacity 0.15s;
- text-decoration: none;
+ display: flex;
+ align-items: center;
+ gap: 0.25rem;
+ white-space: nowrap;
}
+ .dark .prose-spec .clause-link {
+ color: theme(colors.neutral.500);
+ }
+
+ /* Link icon before the clause number */
.prose-spec .clause-link::before {
content: "";
- display: block;
- width: 1rem;
- height: 1rem;
+ flex-shrink: 0;
+ width: 0.875rem;
+ height: 0.875rem;
background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' viewBox='0 0 24 24' stroke-width='2' stroke='%2394a3b8'%3E%3Cpath stroke-linecap='round' stroke-linejoin='round' d='M13.19 8.688a4.5 4.5 0 0 1 1.242 7.244l-4.5 4.5a4.5 4.5 0 0 1-6.364-6.364l1.757-1.757m13.35-.622 1.757-1.757a4.5 4.5 0 0 0-6.364-6.364l-4.5 4.5a4.5 4.5 0 0 0 1.242 7.244'/%3E%3C/svg%3E");
background-size: contain;
background-repeat: no-repeat;
@@ -451,13 +458,22 @@ html {
background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' viewBox='0 0 24 24' stroke-width='2' stroke='%23737373'%3E%3Cpath stroke-linecap='round' stroke-linejoin='round' d='M13.19 8.688a4.5 4.5 0 0 1 1.242 7.244l-4.5 4.5a4.5 4.5 0 0 1-6.364-6.364l1.757-1.757m13.35-.622 1.757-1.757a4.5 4.5 0 0 0-6.364-6.364l-4.5 4.5a4.5 4.5 0 0 0 1.242 7.244'/%3E%3C/svg%3E");
}
- /* Show anchor link on hover - only when not hovering nested lists */
+ /* On hover: show anchor link, hide CSS counter */
.prose-spec ol>li:hover:not(:has(ol:hover))>.clause-link,
.prose-spec ol>li:hover:not(:has(ol:hover))>p>.clause-link,
.prose-spec .clause-link:hover {
opacity: 1;
}
+ .prose-spec ol>li:hover:not(:has(ol:hover))::before {
+ opacity: 0;
+ }
+
+ /* Orange color on direct hover of the link */
+ .prose-spec .clause-link:hover {
+ color: theme(colors.orange.500);
+ }
+
.prose-spec .clause-link:hover::before {
background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' viewBox='0 0 24 24' stroke-width='2' stroke='%23f97316'%3E%3Cpath stroke-linecap='round' stroke-linejoin='round' d='M13.19 8.688a4.5 4.5 0 0 1 1.242 7.244l-4.5 4.5a4.5 4.5 0 0 1-6.364-6.364l1.757-1.757m13.35-.622 1.757-1.757a4.5 4.5 0 0 0-6.364-6.364l-4.5 4.5a4.5 4.5 0 0 0 1.242 7.244'/%3E%3C/svg%3E");
}
diff --git a/src/utils/parseSpecContent.ts b/src/utils/parseSpecContent.ts
index 1462cf7..c4ba60e 100644
--- a/src/utils/parseSpecContent.ts
+++ b/src/utils/parseSpecContent.ts
@@ -229,10 +229,10 @@ function addClauseAnchors(list: List, prefix: string = ""): void {
// Find the first paragraph in the item and prepend an anchor link
for (const child of item.children) {
if (child.type === "paragraph") {
- // Create anchor link HTML to inject
+ // Create anchor link HTML with clause number text
const anchorHtml: Html = {
type: "html",
- value: ``,
+ value: `${clauseNum}.`,
};
// Prepend anchor to paragraph children
(child as { children: RootContent[] }).children.unshift(