I've gone through all the branches we have that are named after a Jira
ticket and was able to delete several merged branches. There are a
couple branches from closed but postponed Jira issues left over which
should clearly be kept as well as some open issues. There are several
named branches
On a related note, I've figured out how to (safely) enable Jenkins for
PR builds now that infra added a GitHub App token. It'll build for
collaborators which includes previous contributors and some other
people that aren't necessarily committers here. If this option works
out well enough, we may
I've updated our Jenkins config to use the GitHub App token recently
configured by Infra rather than using the GitBox setup. Using this, we
can now automatically build PRs from collaborators, though only the
release-2.x and master branches will be deploying snapshots. Most of
these branches and
My mistake; the problems in master appear to be related to test
failures of some sort. I'll see if migrating those tests to JUnit 5
(along with any related refactorings) helps make them less flakey.
On Sat, 22 Aug 2020 at 21:04, Matt Sicker wrote:
>
> Ok, so whatever the issue is is a problem in
Yes, please go ahead and finish the release. The PMC approved this
during our release vote. :)
On Sun, 23 Aug 2020 at 10:22, Apache wrote:
>
> There can’t be. That is what the release vote was for.
>
> Ralph
>
> > On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
> >
> > Thanks Dominik
> >
> >
You'd think we'd see this show up in Jenkins. Interestingly enough, I
am seeing a Windows-specific test failure on Jenkins related to
Spring:
The Log4j release-2.x branch is only there because master is
effectively the "release-3.x" branch right now. We forked the branch
to continue 2.x releases while we started making breaking changes in
the 3.x branch (mostly involving moving plugins around; the API is
still the same).
On Sun, 23 Aug
Since there's no central repository of C++ libraries (or C, or several
other languages for that matter; Rust providing one is a nice change
of pace), it'll be fairly difficult to get real usage stats about what
minimum compiler versions and such are still in use out there. Now I
know it's not the
There can’t be. That is what the release vote was for.
Ralph
> On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
>
> Thanks Dominik
>
> Are there any objections to me pushing the 2.0.9 package that had been
> approved and uploaded to https://downloads.apache.org/logging/log4net/ to
>
I've run into the same issues, and decided to was simpler for me to allow
long path names (on Windows):
https://garygregory.wordpress.com/2019/09/13/enabling-long-path-names-on-windows/
Gary
On Sun, Aug 23, 2020 at 8:10 AM Thorsten Schöning
wrote:
> Hi,
>
> this is a just a hint you might want
Hi,
this is a just a hint you might want to keep in mind:
The currently used naming scheme for "log4j-spring-cloud-config" leads
to some pretty long paths, which under some circumstances and for some
tools result in trouble on Windows. This is a default Windows, without
the setting to support
Guten Tag Robert Middleton,
am Sonntag, 23. August 2020 um 03:31 schrieben Sie:
> I'm working on changes for log4cxx at the moment that involve upgrades to
> use C++11 features; that would definitely require a major change in the
> versioning, although the API would be largely the same.
OTOH,
Guten Tag Ralph Goers,
am Samstag, 22. August 2020 um 19:04 schrieben Sie:
> I didn’t try to run the build from master. I checked out the
> release tag.
The site needed to be updated without new releases in the past
already. I didn't see how this was possible without a branch, so
simply created
Thanks Dominik
Are there any objections to me pushing the 2.0.9 package that had been
approved and uploaded to https://downloads.apache.org/logging/log4net/ to
nuget.org?
-d
On August 23, 2020 09:59:02 Dominik Psenner wrote:
Davyd, I added you as a collaborator. This should grant you
Davyd, I added you as a collaborator. This should grant you the privilege
to manage packages. You can now submit new and update or unlist existing
packages.
It would be great to have at least one other member of the pmc listed as
administrator. The following documents the matrix of permissions.
15 matches
Mail list logo
