Cut release procedure out of README and create specific document for it. I created 'doc/internal' directory for it, dunno if there are more documents to come here. These files won't be distributed in officially released tarballs, of course.
Alternatively, such documents could be on web somewhere. Signed-off-by: Jan Safranek <[email protected]> --- README | 17 ----------------- doc/internal/release.txt | 18 ++++++++++++++++++ 2 files changed, 18 insertions(+), 17 deletions(-) create mode 100644 doc/internal/release.txt diff --git a/README b/README index 93e0aae..54e0f7b 100644 --- a/README +++ b/README @@ -1,20 +1,3 @@ -Please follow the following steps (TODO: Automate these steps) - -0. Update package version in AC_INIT (configure.in) -1. Tag the current sources in trunk to the specified version -1. Run autoreconf -i to generate the configure file again - (on changing any of the automake files) -2. Run configure with --prefix=<desired prefix> default is /usr/local -3. This step should generate - a. Makefile - b. libcgroup.spec -4. To build the RPM, carry out the following steps (obsolete, will be revised) - a. Create a tag with the same version as specified in step 0 - a. Run mktarball - b. copy tarball and spec file to correct place in the RPMBUILD - c. Build an rpm of the spec file - - Design ======== diff --git a/doc/internal/release.txt b/doc/internal/release.txt new file mode 100644 index 0000000..d25fad9 --- /dev/null +++ b/doc/internal/release.txt @@ -0,0 +1,18 @@ +Libcgroup release procedure +=========================== +Please follow the following steps (TODO: Automate these steps) + +0. Update package version in AC_INIT (configure.in) +1. Tag the current sources in trunk to the specified version +1. Run autoreconf -i to generate the configure file again + (on changing any of the automake files) +2. Run configure with --prefix=<desired prefix> default is /usr/local +3. This step should generate + a. Makefile + b. libcgroup.spec +4. To build the RPM, carry out the following steps (obsolete, will be revised) + a. Create a tag with the same version as specified in step 0 + a. Run mktarball + b. copy tarball and spec file to correct place in the RPMBUILD + c. Build an rpm of the spec file + ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Libcg-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libcg-devel
