From: waffel <wa...@ho...> - 2007-08-13 18:10:12
|
Hi, sorry for this huge delay. But my ISP was down for nearly 2 weeks and than I had my year holidays. Now I'am back at home and hope my IPS is stabe so I can create the next release. I think Konstantin is right and we should create a minor version because we have some new features and any bugfixes. I'll wait a little bit about the problem with the cross compiling stuff for ARM. @Konstantin: many thanks for your support! @all others: Thank you for posting on the maillinglist, testing and submitting patches! Hope we can push out the next release with these nice new features and increasing the stability more than once. Regards, - waffel |
From: Konstantin L. <Kon...@ma...> - 2007-08-14 07:34:23
|
Hello, waffel! You wrote to <log...@li...> on Mon, 13 Aug 2007 20:08:49 +0200: w> I think Konstantin is right and we should create a minor version because w> we have some new features and any bugfixes. We have bugfixes. I have fixed appenderMap initinalization bug. Also I have fixed localtime issue, but these changes only in my local copy because I wait until Russ Allbery send me a patch that fix pthread flags. w> I'll wait a little bit about the problem with the cross compiling stuff w> for ARM. w> @Konstantin: many thanks for your support! You are welcome ;) With best regards, Konstantin Litvinenko. |
From: Konstantin L. <Kon...@ma...> - 2007-08-22 06:39:09
|
Hello, waffel! You wrote to <log...@li...> on Mon, 13 Aug 2007 20:08:49 +0200: w> I think Konstantin is right and we should create a minor version because w> we have some new features and any bugfixes. I think we can make new release. What version it will be? 0.3.6? With best regards, Konstantin Litvinenko. |
From: Thomas W. <wa...@ho...> - 2007-08-22 09:47:20
|
Hi Konstantin, Nice ... lets see if I can do this at the weekend. I don't know =20 exactly the new version number ... must have a look into the configure =20 script and wiki how we increase the numbers. But I think you are right =20 ... can be eventual 0.3.6. Regards, - waffel Quoting Konstantin Litvinenko <Kon...@ma...>: > Hello, waffel! > You wrote to <log...@li...> on Mon, 13 Aug 2007 > 20:08:49 +0200: > > w> I think Konstantin is right and we should create a minor version becau= se > w> we have some new features and any bugfixes. > > I think we can make new release. What version it will be? 0.3.6? > > 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 > |
From: Scott C. <can...@os...> - 2007-08-22 14:39:28
|
> I think we can make new release. What version it will be? 0.3.6? Is there some magical criteria for 1.0? Using pre-release numbers doesn't suggest a lot of confidence in the code. -- Scott |
From: Konstantin L. <1da...@ma...> - 2007-08-22 16:00:06
|
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. |
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 |
From: waffel <wa...@ho...> - 2007-08-23 18:12:19
|
Hi, I think also, that the project is old and stable enough to use the 1.0 as the new version number for the upcoming release. - waffel Bastiaan Bakker schrieb: > 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 >> > > > ------------------------------------------------------------------------- > 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 > |