Revision: 1201 Author: sebastien.lelong Date: Sun Aug 16 03:03:25 2009 Log: changelog update http://code.google.com/p/jallib/source/detail?r=1201
Modified: /wiki/ValidationProcess.wiki ======================================= --- /wiki/ValidationProcess.wiki Sun Aug 16 02:18:06 2009 +++ /wiki/ValidationProcess.wiki Sun Aug 16 03:03:25 2009 @@ -32,6 +32,7 @@ # if a new release is created, a new svn branch is created, so we always have access to the release's content at this time. `svn copy https://jallib.googlecode.com/svn/trunk https://jallib.googlecode.com/svn/branches/jallib-the_version` # go to the branch (`svn checkout` it) # edit `tools/Makefile` and change `VERSION=dev` to `VERSION=the_version`. Also replace `trunk` by `branches/jallib-${VERSION}`. This way, one can checkout the branch, and simply `make release` to *exactly* produce the same release packages + # edit CHANGELOG and replace "next" with the actual released version. Also prepare new CHANGELOG in trunk. # just to be sure the branch will contain up-to-date documentation, re-generate it with `make doc` (doc will also be generated from scratch for the packages) # then type `make release 2>&1 | tee release-the_version.log`. Wait a little. packages are available in `distrib` directory. # run `make check` to auto-check all packages, that is make sure all samples compile fine with packages' content --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
