From: Bastiaan B. <bas...@en...> - 2007-08-23 16:42:41
|
Hi, log4cpp's numbering started at 0.1 to show that he first release was very much a work in progress. Then 0.2.x added autoconf based building and 0.3.x threading support. Within each 0.x branch the aim was to keep log4cpp backward compatible on at least API level. Initially 0.2.x was designated 'stable' and 0.3.x 'development' with the intention to let it become a new 0.4.x 'stable'. But that was some time ago (before I handed over the project to Waffel). So go ahead, name it version 1.0. The project is old enough to have a 1.0 :-) Cheers, Bastiaan On Wed, 2007-08-22 at 18:59 +0300, Konstantin Litvinenko wrote: > Hello, Scott! > You wrote to <log...@li...> on Wed, 22 Aug 2007 > 10:39:11 -0400: > > ??>> I think we can make new release. What version it will be? 0.3.6? > > SC> Is there some magical criteria for 1.0? Using pre-release numbers > SC> doesn't suggest a lot of confidence in the code. > > This is very good idea. log4cpp is stable and mature package for a long > time. Why not mirror that in its version as other does? > I vote for 1.0 :) > > With best regards, Konstantin Litvinenko. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Log4cpp-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |