Jenkins build is back to stable : Log4j 2.x #1935

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Performance page

Not the whole site. The source and download links will point to a snapshot. However, we can update individual pages. Ralph > On May 7, 2016, at 8:06 PM, Remko Popma wrote: > > You're asking if it's possible to change the site without doing a release. > I'm not sure, maybe Ralph knows. > >

Re: Performance page

Sure, we can fiddle with site anytime. We just need to make sure that what we publish applies to the current release version. I can get tricky since the site is usually stamped with the POM version. Gary On May 7, 2016 8:06 PM, "Remko Popma" wrote: > You're asking if it's possible to change the

Re: Performance page

You're asking if it's possible to change the site without doing a release. I'm not sure, maybe Ralph knows. Sent from my iPhone > On 2016/05/08, at 11:01, Matt Sicker wrote: > > For the "nice to have" items, can we rebuild the site after 2.6 and just > commit that to svn? Or do site releases

Re: Performance page

For the "nice to have" items, can we rebuild the site after 2.6 and just commit that to svn? Or do site releases always need to match up with the artifacts? On 7 May 2016 at 19:32, Remko Popma wrote: > Understood about Rewrite. > > I figured that the performance page is the last remaining thing

Re: Performance page

Understood about Rewrite. I figured that the performance page is the last remaining thing for the 2.6 release. I had a week off from work and made reasonable progress but it is surprisingly time consuming to create the data and then analyze it and do a write up. Still to do "must have": - J

Re: Performance page

No, I have nothing particular in mind for that. Just to let you know - and not to put any pressure on - I am waiting for this page before we do a release. I think it is pretty important, especially with the detailed results you are producing. Ralph > On May 7, 2016, at 9:33 AM, Remko Popma wr

Re: Jenkins build became unstable: Log4j 2.x #1934

BZ2 again. On Sun, May 8, 2016 at 1:02 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.a

Re: Performance page

Ralph, Started to work on a benchmark to compare Log4j2's File, RandomAccessFile, MemoryMappedFile, Console and Rewrite appenders. Is there any particular scenario you want to test with Rewrite appenders? Remko On Mon, May 2, 2016 at 11:51 PM, Remko Popma wrote: > I will flesh things out furth

Jenkins build became unstable: Log4j 2.x #1934

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-1179) Log4j performance documentation

[ https://issues.apache.org/jira/browse/LOG4J2-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1179: Description: Reorganize and extend performance data on the site. *Async Loggers Manual Page* Shoul

Jenkins build is back to stable : Log4j 2.x #1933

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-1179) Log4j performance documentation

[ https://issues.apache.org/jira/browse/LOG4J2-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1179: Description: Reorganize and extend performance data on the site. *Async Loggers Manual Page* Shoul