Hi Vadim,
> The only major (yet small) thing that I'm going to do is update the
> version number. The plan was the following, if I remember correctly:
>
> name the current version as 1.1.1
> name the beta (to be released in a week or two) as 1.1.2
> name the gold 2.0 as 2.0.0
>
> so, I will change cvver.h and the root CMakeLists.txt to 1.1.1. I
> will appreciate if you update the version in autotools scripts, if
> it has not been done yet. I looked at configure.in and realized that
> I completely forgot that strange libtool version numbering scheme :)
Hm. The autotools version already carries the version number 1.2.1. I
update it from time to time whenever major API incompatibilities pop-
up to make sure everyone using the SVN version gets clean libtool
linking results with the autotools version of OpenCV.
If it poses no problem, we could move change version numbers (CMake
and autotools) to
name the beta (to be released in a week or two) as 1.3.0
name the gold 2.0 as 2.0.0
The libtool version number is unaffected by this. It should be updated
to
name the beta (to be released in a week or two) as 4:0:0
name the gold 2.0 as
4:1:0 in case no interfaces have been changed, added or removed
since beta
5:0:1 in case interfaces have been added but no interface has been
changed or removed since beta
5:0:0 in case interfaces have been changed or removed since beta
Best, Mark
--
Mark Asbach
Institut für Nachrichtentechnik, RWTH Aachen University
http://www.ient.rwth-aachen.de/cms/team/m_asbach ------------------------------------------------------------------------------
_______________________________________________
Opencvlibrary-devel mailing list
Opencvlibrary-devel@...
https://lists.sourceforge.net/lists/listinfo/opencvlibrary-devel
smime.p7s (5K) 