<commit_before>Release Procedure for PAPI  November 07, 2006

Below is a step-wise procedure for making a PAPI release.
This is a living document and may not be totally current or accurate.
It is an attempt to capture current practice in making a PAPI release.
Please update it as appropriate.

One way to use this procedure is to print a copy and check off
the lines as they are completed to avoid confusion.
================================================================================
__ 1. Notify developers that a release is imminent and the repository should be
	considered frozen.

__ 2. Create a ChangeLog for the current release. 
	- One handy way to do this is to use the python script that comes with
	WinCVS:
	  Macros->CVS->Build ChangeLog (advanced).
	Use the -r<branch>: command to log commit messages from the previous 
	branch point to the present.

__ 3. Scan the ChangeLog to remove extraneous fluff, like perfctr imports.

__ 4. Modfy RELEASENOTES.txt to summarize the major changes listed in the log.

__ 5. Check/Change the version number in papi.h, and commit to cvs if needed.

__ 6. Add ChangeLogXYZ.txt to cvs and commit both ChangeLogXYZ.txt and 
	RELEASENOTES.txt.

__ 7. Export the PAPI FAQ to PAPI_FAQ.html in case anything changed.

__ 8. Update and commit any man pages that changed.

__ 9. Update and commit any other documentation that changed.

__ 10. Branch cvs.

__ 11. Export the branch to a clean working directory:
	> cvs export -r <branch> <module> ex:
	> cvs export -r papi-3-2-0 papi

__ 12. Delete any unneccessary files or directories

__ 13. Rename the directory from papi to papi-X.Y.Z

__ 14. tar the directory:
	> tar -cvf papi-X.Y.Z.tar papi-X.Y.Z

__ 15. zip the tarball:
	gzip papi-X.Y.Z.tar

__ 16. Copy the tarball to icl:/sw/www/icl/projects/papi/downloads
<commit_msg>Document where version numbers must be changed.<commit_after>Release Procedure for PAPI  November 07, 2006

Below is a step-wise procedure for making a PAPI release.
This is a living document and may not be totally current or accurate.
It is an attempt to capture current practice in making a PAPI release.
Please update it as appropriate.

One way to use this procedure is to print a copy and check off
the lines as they are completed to avoid confusion.
================================================================================
__ 1. Notify developers that a release is imminent and the repository should be
	considered frozen.

__ 2. Create a ChangeLog for the current release. 
	- One handy way to do this is to use the python script that comes with
	WinCVS:
	  Macros->CVS->Build ChangeLog (advanced).
	Use the -r<branch>: command to log commit messages from the previous 
	branch point to the present.

__ 3. Scan the ChangeLog to remove extraneous fluff, like perfctr imports.

__ 4. Modfy RELEASENOTES.txt to summarize the major changes listed in the log.

__ 5. Check/Change the version number in: papi.h, configure.in, Makefile.in;
	and commit to cvs if needed.

__ 6. Add ChangeLogXYZ.txt to cvs and commit both ChangeLogXYZ.txt and 
	RELEASENOTES.txt.

__ 7. Export the PAPI FAQ to PAPI_FAQ.html in case anything changed.

__ 8. Update and commit any man pages that changed.

__ 9. Update and commit any other documentation that changed.

__ 10. Branch cvs.

__ 11. Export the branch to a clean working directory:
	> cvs export -r <branch> <module> ex:
	> cvs export -r papi-3-2-0 papi

__ 12. Delete any unneccessary files or directories

__ 13. Rename the directory from papi to papi-X.Y.Z

__ 14. tar the directory:
	> tar -cvf papi-X.Y.Z.tar papi-X.Y.Z

__ 15. zip the tarball:
	gzip papi-X.Y.Z.tar

__ 16. Copy the tarball to icl:/sw/www/icl/projects/papi/downloads

{'fraction_non_alphanumeric': 0.09685230024213075, 'fraction_numerical': 0.017218186709712133, 'mean_word_length': 3.7003792667509483, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 19, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5769276', 'n_tokens_mistral': 1191, 'n_tokens_neox': 1094, 'n_words': 534}