summaryrefslogtreecommitdiffstats
path: root/VERSION
Commit message (Collapse)AuthorAgeFilesLines
* Become IPA v2 RC 3 (2.0.0.rc3)Rob Crittenden2011-03-101-1/+1
|
* Become IPA v2 RC 2 (2.0.0.rc2)Rob Crittenden2011-02-231-1/+1
|
* Become IPA v2 RC 1 (2.0.0.rc1)Rob Crittenden2011-02-141-2/+2
|
* Become IPA v2 beta 2 (2.0.0.pre2)Rob Crittenden2011-02-101-1/+1
|
* Add API version and have server reject incompatible clients.Rob Crittenden2011-01-141-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | This patch contains 2 parts. The first part is a small utility to create and validate the current API. To do this it needs to load ipalib which on a fresh system introduces a few problems, namely that it relies on a python plugin to set the default encoding to utf8. For our purposes we can skip that. It is also important that any optional plugins be loadable so the API can be examined. The second part is a version exchange between the client and server. The version has a major and a minor version. The major verion is updated whenever existing API changes. The minor version is updated when new API is added. A request will be rejected if either the major versions don't match or if the client major version is higher than then server major version (though by implication new API would return a command not found if allowed to proceed). To determine the API version of the server from a client use the ping command. ticket 584
* Become IPA v2 beta 1 (2.0.0.pre1)Rob Crittenden2010-12-221-3/+3
|
* Become IPA v2 alpha 5 (1.9.0.pre5)Rob Crittenden2010-11-091-1/+1
|
* Become IPA v2 alpha 4 (1.9.0.pre4)alpha_4-1-9-0Rob Crittenden2010-07-151-1/+1
|
* Replication version checking.Rob Crittenden2010-06-241-0/+13
| | | | | | | | 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)alpha_3-1-9-0Rob Crittenden2010-05-071-1/+1
|
* Become IPA v2 alpha 2 (1.9.0.pre2)alpha_2-1-9-0Rob Crittenden2010-02-181-1/+1
|
* Back down to version 1.9.0 in preparation for release of first alpha.alpha-1-9-0Rob Crittenden2009-10-261-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.0pre1Rob Crittenden2009-05-111-3/+3
|
* Bump up version number to 1.2.0Simo Sorce2008-11-131-2/+2
|
* Fix versioning for configure.ac and ipa-python/setup.pySimo Sorce2008-08-111-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-0Simo Sorce2008-06-111-1/+1
|
* Redo the way versioning works in freeIPA.Rob Crittenden2008-05-051-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
generated by cgit (git 2.34.1) at 2024-11-16 06:13:46 +0000