The major reason for bumping the version to 2.14.0 was the expectation that
JsonTemplateLayout would be added to the release-2.x branch. Is there anything
standing in the way of that? There is enough stuff in the branch that once that
is merged I’d like to do a release as soon as I can find the
Hey all,
I'd like to propose some new features/updates for log4cxx, if there's
interest. A number of these are rather large changes, so it probably
doesn't make sense to work on them until there's a known-good release, as
they would likely break both API and ABI compatibility.
Big Changes:
I am going to vote +1 (binding) on this release. Although it does need to be
signed I am comfortable with either Matt or myself signing it before it is
uploaded as Davyd’s signing key isn’t going to be signed by anyone if he has
never had a key before. One of us is going to have to publish this
Have they ever worked? I don’t think we need Jenkins, Travis and GitHub Actions.
Ralph
> On Aug 2, 2020, at 12:03 PM, Matt Sicker wrote:
>
> As far as I can tell, we have full support for building PRs in both
> Windows and Linux (and macOS supposedly, though I haven't tried that
> out) on
Here's some info for you:
https://infra.apache.org/release-signing.html
And some general info about release publishing:
https://infra.apache.org/release-publishing.html
On Sun, 2 Aug 2020 at 14:47, Davyd McColl wrote:
>
> Having never signed release artifacts before, I'm likely to Do It
Having never signed release artifacts before, I'm likely to Do It Wrong. Is
there any Signing For Dummies you could recommend to get going on the right
foot?
-d
On August 2, 2020 21:31:43 Matt Sicker wrote:
So far it looks good (though I'm not a .net developer, so I can't
speak from that
So far it looks good (though I'm not a .net developer, so I can't
speak from that side). There's one more thing we need from this to
make it a proper release. You'll need to add a GPG signature for the
artifacts as well. We'll need to import your signing key to
I'm in favor of consolidation, I don't recall Travis working on both master and
release-2.x at the same time. Thanks for your work to improve the build
pipeline, Matt!
-ck
On Sun, Aug 2, 2020, at 15:03, Matt Sicker wrote:
> As far as I can tell, we have full support for building PRs in both
>
As far as I can tell, we have full support for building PRs in both
Windows and Linux (and macOS supposedly, though I haven't tried that
out) on GitHub Actions. With that configured, I don't think it's
necessary to also run PRs on Travis, especially if their
configurations get out of sync and