<commit_before>Release Procedure for PAPI  Nov 02, 2011

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. Update any documentation that may have changed. Pay particular attention
	to INSTALL.txt.

__ 3. Check/Change the version number in: papi.spec, papi.h, configure.in, Makefile.in,
	Doxyfile, Doxyfile-everything, Doxyfile.utils (PROJECT_NUMBER) ; and commit to cvs if needed.

-- 3a. On most icl machines:
	export PATH=/mnt/scratch/doxygen-1.7.5.1/bin:$PATH
	-- or --
	setenv PATH /mnt/scratch/doxygen-1.7.5.1/bin:$PATH

-- 3b. Rebuild the doxygen manpages (  cd doc && make && make install )
	You will want to check if anything needs to be committed to cvs.
<commit_msg>release_procedure now reflects the correct version of doxygen to use.<commit_after>Release Procedure for PAPI  Nov 02, 2011

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. Update any documentation that may have changed. Pay particular attention
	to INSTALL.txt.

__ 3. Check/Change the version number in: papi.spec, papi.h, configure.in, Makefile.in,
	Doxyfile, Doxyfile-everything, Doxyfile.utils (PROJECT_NUMBER) ; and commit to cvs if needed.

-- 3a. On most icl machines:
	export PATH=/mnt/scratch/doxygen-1.7.4/bin:$PATH
	-- or --
	setenv PATH /mnt/scratch/doxygen-1.7.4/bin:$PATH

-- 3b. Rebuild the doxygen manpages (  cd doc && make && make install )
	You will want to check if anything needs to be committed to cvs.

{'fraction_non_alphanumeric': 0.12920875420875422, 'fraction_numerical': 0.015151515151515152, 'mean_word_length': 4.089935760171306, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6848551', 'n_tokens_mistral': 710, 'n_tokens_neox': 652, 'n_words': 315}