projects
/
mmh
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
spost accept body lines with 998 characters
[mmh]
/
docs
/
README.releasing
diff --git
a/docs/README.releasing
b/docs/README.releasing
index
c526fb3
..
fbc9877
100644
(file)
--- a/
docs/README.releasing
+++ b/
docs/README.releasing
@@
-11,20
+11,18
@@
here):
1. % echo 1.0 > VERSION
% date +"%Y-%m-%d" > DATE
1. % echo 1.0 > VERSION
% date +"%Y-%m-%d" > DATE
- (DATE should contain something like "2012-12-08")
+ % vi NEWS
- 2. % git commit VERSION DATE; git push
+ 2. % git commit VERSION DATE NEWS
- 3. % git tag -a mmh-1.0 -m 'Releasing mmh-1.0'
+ 3. % make mmhdist
- 4. % make mmhdist
-
- 5. Untar mmh-1.0.tar.gz and `diff -r' it vs. your workspace. Make
+ 4. Untar mmh-1.0.tar.gz and `diff -r' it vs. your workspace. Make
sure no files got left out of the distribution that should be in
it (due to someone forgetting to update the DIST variables in the
Makefiles).
sure no files got left out of the distribution that should be in
it (due to someone forgetting to update the DIST variables in the
Makefiles).
- 6. If you have root access on your machine, it's good at this point
+ 5. If you have root access on your machine, it's good at this point
to do:
% chown -R 0:0 mmh-1.0
to do:
% chown -R 0:0 mmh-1.0
@@
-35,15
+33,19
@@
here):
being installed, making it possible for that user to Trojan the mmh
code before the system administrator finishes installing it.
being installed, making it possible for that user to Trojan the mmh
code before the system administrator finishes installing it.
- 7. Make sure your new tarball uncompresses and untars with no problem.
+ 6. Make sure your new tarball uncompresses and untars with no problem.
Make sure you can configure, make, and install mmh from it.
Make sure you can configure, make, and install mmh from it.
- 8. If all is well and your tarball is final, go back to your workspace
- and do:
+ 7. If all is well and your tarball is final, go back to your workspace
+ and tag the release:
+
+ % git tag -a mmh-1.0 -m 'Releasing mmh-1.0'
+
+ 8. Then bump the version number:
% echo 1.0+dev > VERSION
% echo 1.0+dev > VERSION
- 9. % git commit VERSION; git push
+ 9. % git commit VERSION
10. Generate an MD5 hash and a PGP signature of the tarball:
10. Generate an MD5 hash and a PGP signature of the tarball: