Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Apache announcements sent to the announcement list have a few requirements. They should include a link to the web site and must include a link to the download page near the front of the email. As Matt said, they must look like they come from your apache.org email address. I

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Make sure to move the tag into a rel/ namespaced tag. Those are immutable. For announcing, make sure to send from your Apache email and CC annou...@apache.org. On Mon, Aug 24, 2020 at 12:35 Robert Middleton wrote: > Since we have an actual release now, should we make an announcement email > > on

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Since we have an actual release now, should we make an announcement email on the gene...@logging.apache.org list? I can write up a blurb, but I'm not sure who can post to that list. I've also updated the tag for the release appropriately(v0.11.0) -Robert Middleton On Sun, Aug 23, 2020 at 1:09 P

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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 o

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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. >

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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 update

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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 by

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

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

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

I tried running mvn site for log4cxx and it failed. Since the pom is still 0.11.0-SNAPSHOT everything that refers to the version would be wrong. If I just patch the download page then the changes page won’t reflect whatever was done in 0.11.0. I also noticed that the source links are pointing to

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

I have moved the files to the release folder. I will look at updating the web site. Ralph > On Aug 18, 2020, at 4:49 PM, Ralph Goers wrote: > > I’ll take care of it. > > Ralph > >> On Aug 18, 2020, at 3:46 PM, Robert Middleton wrote: >> >> By my count at this point, that means we have 3 bi

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

I’ll take care of it. Ralph > On Aug 18, 2020, at 3:46 PM, Robert Middleton wrote: > > By my count at this point, that means we have 3 binding +1 votes from > Ralph, Christian, Remko; and +1 votes from Thorsten and Stephen. > > Ralph, do you want to upload to the releases repo with the fix for

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

By my count at this point, that means we have 3 binding +1 votes from Ralph, Christian, Remko; and +1 votes from Thorsten and Stephen. Ralph, do you want to upload to the releases repo with the fix for the .sha file, or do you want me to do that?(it is a SHA-512, it's just named incorrectly) -Rob

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

I am using a recent version in production Ubuntu servers, so it is definitely release ready. +1 On Mon, Aug 17, 2020, 7:27 PM Christian Grobmeier wrote: > Hello, > > I am not an expert on c++ or something, but I looked on the content, read > this thread and think it is safe to release this. Howe

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Hello, I am not an expert on c++ or something, but I looked on the content, read this thread and think it is safe to release this. However, my hope is that in future more competent cxx devs than me would check it :) I vote +1 also Cheers, Christian On Mon, Aug 17, 2020, at 08:08, Ralph Goers

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Guten Tag Ralph Goers, am Montag, 17. August 2020 um 08:08 schrieben Sie: > I noticed that the files have she and md5 files. We are not > supposed to use either of these any more and only use sha512. I can fix that. While the file extension is named ".sha", SHA-512 is calculated already: > gpg -

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

I noticed that the files have she and md5 files. We are not supposed to use either of these any more and only use sha512. I can fix that. I vote +1 Ralph > On Aug 9, 2020, at 10:24 AM, Robert Middleton wrote: > > I've run through the release of log4cxx 0.11.0. There's still something > st

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Guten Tag Robert Middleton, am Donnerstag, 13. August 2020 um 05:52 schrieben Sie: > [...]Windows has 8 failures(some are timeout, some have to > do with encoding, and possibly some other issues as well). At this point > that makes me much less confident in everything working properly, so > perha

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Ralph, Thanks for taking a look at it whenever you get a chance. Also to note: I did manage to get it building via Github actions, and while Linux(Ubuntu) works fine, OSX has one test failure(the same that you saw the other week), and Windows has 8 failures(some are timeout, some have to do with

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Yeah - ideally this would be done within 72 hours but that doesn’t always happen - especially since this is the first release in a long, long time. I have been planning on reviewing it but probably can’t get to it until tomorrow. Ralph > On Aug 12, 2020, at 6:34 PM, Robert Middleton wrote: >

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

So I realize that I never set a normal time for this vote to be open, but it has been 72 hours at this point. Do people still need more time to validate, or are there some issues that need to be resolved first? -Robert Middleton On Mon, Aug 10, 2020 at 5:49 PM Remko Popma wrote: > +1 > Remko.

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

+1 Remko. > On Aug 11, 2020, at 6:27, Robert Middleton wrote: > > This new RC has the latest fixes that we've done(LOG4CXX-512,490,398). > > I'm not sure exactly why the autotools are there now; something about doing > the maven release triggers them. I don't think they get generated until

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

This new RC has the latest fixes that we've done(LOG4CXX-512,490,398). I'm not sure exactly why the autotools are there now; something about doing the maven release triggers them. I don't think they get generated until after the website gets uploaded, which I couldn't do before. They /should/ be

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

Guten Tag Robert Middleton, am Sonntag, 9. August 2020 um 19:24 schrieben Sie: > Artifacts uploaded here: > https://dist.apache.org/repos/dist/dev/logging/log4cxx/ > tag: https://github.com/apache/logging-log4cxx/tree/v0.11.0-RC2 +1 for me. Do you know what's the difference compared to what you

[VOTE] [log4xx] Release log4cxx 0.11.0

I've run through the release of log4cxx 0.11.0. There's still something strange about how it all works(mostly due to the tooling of shell script/maven/ant/cmake/autotools). However, I do believe that I have a workable release at this point. A quick note on the release: I did the 'mvn release:pre