freeipa.git/VERSION, branch webui-cleanup

Become IPA v2 alpha 4 (1.9.0.pre4)

2010-07-15T15:25:39+00:00

Replication version checking.

2010-06-24T14:33:53+00:00

Whenever we upgrade IPA such that any data incompatibilities might occur
then we need to bump the DATA_VERSION value so that data will not
replicate to other servers. The idea is that you can do an in-place
upgrade of each IPA server and the different versions own't pollute
each other with bad data.

Become IPA v2 alpha 3 (1.9.0.pre3)

2010-05-07T17:22:39+00:00

Become IPA v2 alpha 2 (1.9.0.pre2)

2010-02-18T16:29:16+00:00

Back down to version 1.9.0 in preparation for release of first alpha.

2009-10-26T17:55:01+00:00

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

2009-05-11T20:26:55+00:00

Bump up version number to 1.2.0

2008-11-13T16:20:06+00:00

Fix versioning for configure.ac and ipa-python/setup.py

2008-08-11T22:31:05+00:00

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 release

2008-06-11T13:21:18+00:00

Redo the way versioning works in freeIPA.

2008-05-05T17:53:57+00:00

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