freeipa.git - Unnamed repository; edit this file to name it for gitweb.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Become IPA v2 alpha 2 (1.9.0.pre2)	Rob Crittenden	2010-02-18	1	-1/+1
\|
*	Back down to version 1.9.0 in preparation for release of first alpha.	Rob Crittenden	2009-10-26	1	-2/+2
\| \| \| \| \| \| \|	There was much back and forth and gnashing of teeth about what the version should actually be in these pre-releases. We decided it isn't 2.0-ish enough so went with 1.9.0, 1.9.1, etc until we're ready to declare 2.0.0.
*	Bump version to 2.0.0pre1	Rob Crittenden	2009-05-11	1	-3/+3
\|
*	Bump up version number to 1.2.0	Simo Sorce	2008-11-13	1	-2/+2
\|
*	Fix versioning for configure.ac and ipa-python/setup.py	Simo Sorce	2008-08-11	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	Fix make maintainer-clean Also make RPM naming consistent by using a temp RELEASE file. This one helps when testing builds using rpms. Just 'echo X > RELEASE' to build a new rpms (X, X+1, X+2 ...) Version 1.1.0 was released some times ago, bump up to 1.1.1
*	Move version to 1.1.0 in preparation for new patch releaserelease-1-1-0	Simo Sorce	2008-06-11	1	-1/+1
\|
*	Redo the way versioning works in freeIPA.	Rob Crittenden	2008-05-05	1	-0/+55
	The file VERSION is now the sole-source of versioning. The generated .spec files will been removed in the maintainer-clean targets and have been removed from the repository. By default a GIT build is done. To do a non-GIT build do: $ make TARGET IPA_VERSION_IS_GIT_SNAPSHOT=no When updating the version you can run this to regenerate the version: $ make version-update The version can be determined in Python by using ipaserver.version.VERSION