rgoers edited a comment on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657133838
To get a release out someone needs to create whatever the PMC is going to
vote on. If it is just a source release then that should be packaged in gzip
and/or zip forma
rgoers commented on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657133838
To get a release out someone needs to create whatever the PMC is going to
vote on. If it is just a source release then that should be packaged in gzip
and/or zip format. If t
fluffynuts edited a comment on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657108333
Uhm... so ok, this is merged, but how does a release now get out? 2.0.9 has
been ready for release for a while, without happening, long before I got
involved. It's
fluffynuts edited a comment on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657108333
Uhm... so ok, this is merged, but how does a release now get out? 2.0.9 has
been ready for release for a while, without happening, long before I got
involved. It's
fluffynuts commented on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657108333
Uhm... so ok, this is merged, but how does a release now get out? 2.0.9 has
been ready for release for a while, without happening, long before I got
involved. It's all we
rgoers edited a comment on pull request #383:
URL: https://github.com/apache/logging-log4j2/pull/383#issuecomment-657105873
Just a reminder that these were only merged to master so will not affect the
active web site. The release-2.x branch doesn't use asciidoc for this page so
the change
rgoers commented on pull request #384:
URL: https://github.com/apache/logging-log4j2/pull/384#issuecomment-657106035
Just a reminder that these changes were only merged to master so will not
affect the live web site.
This is
rgoers commented on pull request #383:
URL: https://github.com/apache/logging-log4j2/pull/383#issuecomment-657105873
Just a reminder that these were only merged to master so will not affect the
active web site.
This is an au
vy commented on pull request #384:
URL: https://github.com/apache/logging-log4j2/pull/384#issuecomment-657103113
Keep them coming @janmaterne! Thanks!
This is an automated message from the Apache Git Service.
To respond to th
vy merged pull request #384:
URL: https://github.com/apache/logging-log4j2/pull/384
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
vy commented on pull request #383:
URL: https://github.com/apache/logging-log4j2/pull/383#issuecomment-657102850
Thanks so much @janmaterne! Merged.
This is an automated message from the Apache Git Service.
To respond to the
vy merged pull request #383:
URL: https://github.com/apache/logging-log4j2/pull/383
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
There is a build failure in log4j/master.
Build: https://builds.apache.org/job/log4j/job/master/98/
Logs: https://builds.apache.org/job/log4j/job/master/98/console
Test results: https://builds.apache.org/job/log4j/job/master/98/testReport/
Changes: https://builds.apache.org/job/log4j/job/master/9
rm5248 commented on pull request #59:
URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-657059780
For Ralph: If you don't know, Microsoft does provide development VMs that
already have the tools installed so you don't need to download Visual Studio
and .NET:
https://deve
14 matches
Mail list logo