I am using a recent version in production Ubuntu servers, so it is definitely release ready. +1
On Mon, Aug 17, 2020, 7:27 PM Christian Grobmeier <grobme...@apache.org> wrote: > Hello, > > I am not an expert on c++ or something, but I looked on the content, read > this thread and think it is safe to release this. However, my hope is that > in future more competent cxx devs than me would check it :) > > I vote +1 also > > Cheers, > Christian > > On Mon, Aug 17, 2020, at 08:08, Ralph Goers wrote: > > I noticed that the files have she and md5 files. We are not supposed to > > use either of these any more and only use sha512. I can fix that. > > > > I vote +1 > > > > Ralph > > > > > > > > > > > On Aug 9, 2020, at 10:24 AM, Robert Middleton <osfan6...@gmail.com> > wrote: > > > > > > I've run through the release of log4cxx 0.11.0. There's still > something > > > strange about how it all works(mostly due to the tooling of shell > > > script/maven/ant/cmake/autotools). However, I do believe that I have a > > > workable release at this point. A quick note on the release: I did the > > > 'mvn release:prepare' manually, which is where these artifacts come > from; > > > running through the 'mvn release:perform' causes the generated files > to be > > > -SNAPSHOT versioned, instead of 0.11.0. This means that the version > of the > > > pom.xml in the tag is still 0.11.0-SNAPSHOT, but since maven isn't > really > > > used to build I don't think this will be an issue. > > > > > > Artifacts uploaded here: > > > https://dist.apache.org/repos/dist/dev/logging/log4cxx/ > > > tag: https://github.com/apache/logging-log4cxx/tree/v0.11.0-RC2 > > > > > > The artifacts are signed, although I still need to send my key to Matt > so > > > he can import it into the logging KEYS file. > > > > > > -Robert Middleton > > > > > > >
