summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING10
1 files changed, 5 insertions, 5 deletions
diff --git a/RELEASING b/RELEASING
index 2fa24f0be..a1edceba9 100644
--- a/RELEASING
+++ b/RELEASING
@@ -1,13 +1,13 @@
Here are the steps to follow to create a new cairo release:
-1) Ensure that there are no local, uncommitted/unspushed
+1) Ensure that there are no local, uncommitted/unpushed
modifications. You're probably in a good state if both "git diff
HEAD" and "git log master..origin/master" give no output.
2) Verify that the code passes "make distcheck"
First, make sure you have 'nm' and 'readelf' commands in PATH.
- this should be Ok with any Linux distro.
+ this should be OK with any Linux distro.
Running "make distcheck" should result in no warnings or
errors and end with a message of the form:
@@ -43,7 +43,7 @@ Here are the steps to follow to create a new cairo release:
3) Fill out an entry in the NEWS file
Sift through the logs since the last release. This is most
- easily done with a comand such as:
+ easily done with a command such as:
git log --stat X.Y.Z..
@@ -72,7 +72,7 @@ Here are the steps to follow to create a new cairo release:
and reset cairo_version_micro to 0. NOTE: The minor version is
only incremented for releases, not for snapshots.
- Otherwise, (ie. there are only bug fixes), increment
+ Otherwise, (i.e. there are only bug fixes), increment
cairo_version_micro to the next larger (even) number.
5) Commit the changes to NEWS and cairo-version.h
@@ -124,7 +124,7 @@ Here are the steps to follow to create a new cairo release:
using the text provided from "make release-publish", adding the excerpt
from NEWS, your signature, followed by the standard "What is cairo" and
"Where to get more information about cairo" blurbs from README, and
- inally the shortlog of all changes since last release, generated by:
+ finally the shortlog of all changes since last release, generated by:
git shortlog X.Y.Z...