That is for those involved in the C++ development to decide but I would wonder
a) Besides updating the compiler are there other architectural improvements
that should be made.
b) How much will the code diverge - would it be possible to share the code that
is in common somehow or would that just
Ok, so whatever the issue is is a problem in both branches now.
On Fri, 21 Aug 2020 at 09:56, Matt Sicker wrote:
>
> I’ve been modifying build settings in master lately that haven’t been merged
> back to this branch. I’d assume there’s a difference in the pom file here.
> I’ll take a closer
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. Part of the
question with that as well is what platforms and compilers are supported,
as
I would completely support that change.
On Sun, Aug 23, 2020, 3:14 AM Ralph Goers
wrote:
> In looking at the log4cxx changelog I can’t help notice that the first
> release was 17 years ago. After all these years one would expect that the
> version should have hit 1.0.0 at least 10-15 years ago.
Oh ok, well, mine is davydm (:
-d
On August 22, 2020 20:49:59 Dominik Psenner wrote:
Apparently it cant be the email but must be the nuget accounts username,
apologies.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sat, Aug 22, 2020, 20:39 Davyd
Apparently it cant be the email but must be the nuget accounts username,
apologies.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote:
> I know I'm quite new, but I'm happy to push approved packages. My
> Microsoft
>
I know I'm quite new, but I'm happy to push approved packages. My Microsoft
account for nuget is this email address (dav...@gmail.com)
-d
On August 22, 2020 19:46:45 Dominik Psenner wrote:
Hi
I recall that we were forced to transform the nuget account Apache.Logging (
Hi
I recall that we were forced to transform the nuget account Apache.Logging (
https://www.nuget.org/profiles/Apache.Logging) from a personal account into
an organization. I am currently the only member and administrator of that
organization. Please share with me (may also be in private) the
In looking at the log4cxx changelog I can’t help notice that the first release
was 17 years ago. After all these years one would expect that the version
should have hit 1.0.0 at least 10-15 years ago. Isn’t it time to correct that?
Ralph
Wow. I just noticed that it was 12 years since the last release. A little
overdue I think. Great going guys. Keep up the good work!
Ralph
> On Aug 22, 2020, at 10:07 AM, Ralph Goers wrote:
>
> Please disregard the last sentence below. The site must have been cached. It
> shows 0.11.0 now.
>
Please disregard the last sentence below. The site must have been cached. It
shows 0.11.0 now.
Ralph
> On Aug 22, 2020, at 10:04 AM, Ralph Goers wrote:
>
> I didn’t try to run the build from master. I checked out the release tag. The
> normal process with the maven release plugin is to
I didn’t try to run the build from master. I checked out the release tag. The
normal process with the maven release plugin is to update the version to the
release version on master, create a tag, and then update the version to the
next development version. The release build is then performed
Hearing no objections, I'll continue with this release.
On Sun, 16 Aug 2020 at 13:53, Matt Sicker wrote:
>
> It's been over two years since the last parent POM release. In that
> time, its own parent POM has been upgraded from version 19 to version
> 23. We don't really have any other explicit
Guten Tag Ralph Goers,
am Freitag, 21. August 2020 um 23:42 schrieben Sie:
> At this point I am not sure how to update the site.
TL;DR:
The site describing the latest release is not supposed to be updated
from MASTER. Sources need to be merged to "latest_stable", revision
numbers, release dates
14 matches
Mail list logo
