We are working to get 1.2.14 deployed into our development and QA environments this iteration. I’ll let you know. Once we get it into production, it’ll be logging at a many thousands of lines per second rate on each system. We primarily use the syslog appender. One of our two primary systems is extensively based on async/await (no-UI thread, no UI synchronization context) and our logging relies heavily on logical thread context being preserved across await calls. So at least for this issue we should know pretty quickly if that problem is solved, and we’ll have a good idea of general engine stability. I’ll let you know as we get this rolled out.
I could try to setup ADO.NET <http://ado.net/> appender in my development environment and run my development traffic against it if that’s helpful. > On Nov 20, 2015, at 5:27 AM, Stefan Bodewig <bode...@apache.org> wrote: > > Hi all > > I assume nobody other than me has got an environment to build a new > release. I can't say I enjoy the process and it takes quite a bit of > time so I'd prefer to avoid building more archives than necessary. > > So far we know there is a problem with the ADO.NET appender that > requires a new release. And I recall Jeremiah wanted to give 1.2.14 a > more thorrough testing. Is there anything else we are waiting for? > > Stefan
