There are not many important changes. It looks like really only the following has changed:
* LOGCXX-556 - issue with the syslog appender * Multiple process support for the BufferedWriter * Fix the build with Qt * Mocking the clock(really only relevant for unit tests) * Static initialization updates The good news is that making the release is very easy at this point. All you have to do is to define APACHE_MAINTAINER and do 'make dist' to generate the tar.gz/zip files and the checksums, build and upload the site to staging, and upload the binaries to the SVN repo for voting on. -Robert Middleton On Mon, Sep 26, 2022 at 9:13 PM Stephen Webb <swebb2...@gmail.com> wrote: > > I just went through the differences between master and rel/v0.13.0 and the > only significant fix I saw in master was the crash in a statically linked > log4cxx library. > > While I am not familiar with the amount of work required to create a > release (it looks like a lot), I wonder if there are enough changes in > master to justify the work of creating a release. > > On Tue, Sep 27, 2022 at 11:02 AM Robert Middleton <osfan6...@gmail.com> > wrote: > > > On Mon, Sep 26, 2022 at 5:09 AM Thorsten Schöning <tschoen...@am-soft.de> > > wrote: > > > > * Having better error reporting - many exceptions that are thrown are > > > > basically swallowed and just print out to stderr at the moment. Come > > > > to think of it, do we even want exceptions? It seems like a bad idea > > > > for the logging framework to throw exceptions > > > > > > What else do you have in mind, some error handlers and callbacks? > > > Throwing and swallowing at some point doesn't sound that bad, as long > > > as the problem is visible somewhere. Logback pretty mich logs on > > > STDERR or STDOUT only as well. > > > > > > > Yes, error handling and/or callbacks to notify the user. There are > > certain situations where there isn't much useful information available > > unless you're looking at STDERR, and even sometimes that information > > is pretty useless. For example, if you try to use the DOMConfigurator > > and the file isn't found, the only way for you to tell that something > > went wrong is to view the output of the process; this should probably > > return a bool or something to indicate that the configuration was > > successful or not. > > > > And then there's the incredibly unhelpful error message of "please > > initialize the log4cxx system properly" which should probably print > > out a bit more as to what it tried to do and why it failed. > > > > -Robert Middleton > >
