What you are seeing is exactly what I have been saying. The major problem is
that none of the existing logging services committers know how to perform a
release. We know there have been fixes committed that are needed. We just don’t
know how to make them available. That is exactly why I said you
I'm glad to help -- not sure where though:
I'm sure I could build (haven't actually done it) log4net and the associated
package, and I could push that to nuget from my own machine, assuming that I
had the credentials to do so. Releasing my own packages is the least work I
have to do when I make
We mostly develop on the JVM which has a fairly different build
system. Performing a release for the .net code seems to involve
multiple build tools, and our old CI setup for log4net is broken due
to nant no longer being included in our Jenkins nodes. Basically, the
only realistic release we can va
Ok, so would it be acceptable to change the build system altogether? Should I
create a PR using the build system (npm / node-based) that I use for my
projects? I'm happy to do so.
-d
On 2020-04-07 17:39:31, Matt Sicker wrote:
We mostly develop on the JVM which has a fairly different build
syste
You'll want to make sure the website (or _a_ website) and
documentation are still generated nicely. I see there's still a
pom.xml which is likely used for generating the website (pom.xml is
usually use for JVM-based builds in general, but we've re-used it for
website generation on the other log4* s
You should feel free to change the build system in any way that makes it easier
for people to perform a release. Ideally, it would be nice if it was something
that could be automated from Jenkins, but that is not a requirement.
Ralph
> On Apr 7, 2020, at 8:42 AM, Davyd McColl wrote:
>
> Ok,
Speaking of the Jenkins build, if you want to use Docker images to
create a build environment, that's also supported.
On Tue, 7 Apr 2020 at 10:46, Ralph Goers wrote:
>
> You should feel free to change the build system in any way that makes it
> easier for people to perform a release. Ideally, it
Hello,
There are a couple of concerns I want to share regarding the available
JSON quoting options in the core. I would appreciate your feedback on
them.
1. My first concern is... There are 2 competing JSON quoting
implementations in the core:
- JsonUtils.quoteAsString(CharSequence, String
Thanks Matt
To clarify my plans, I will:
1. update the build system for log4net: I haven't seen any objection to using
node-based build scripts as I have for my own packages, so I'll head down that
path. Currently, I use those as a git submodule, but I'm quite close to having
them available as
Sounds good. If you wouldn’t mind, it would be nice if you could provide
progress reports on a regular schedule that works for you just so we know you
are still working on it.
Also, as you probably know we do get PRs and questions from time to time that
none of us are comfortable answering. It
On progress reports: sure, I'll try to keep this list updated
On PRs: I'm happy to start helping once I've spent more time in the codebase
(which I will have to do anyway), so that I can give better feedback.
-d
On 2020-04-08 08:53:44, Ralph Goers wrote:
Sounds good. If you wouldn’t mind, it wou
11 matches
Mail list logo
