Re: 2.17.3 vs 2.18.0
We need to get the web site build straightened out and I would really like to have either RevAPI fixed or a replacement. We need to know about breaking changes. However, I am not holding out hope for RevAPI. It is pretty much a one man show and he hasn’t given it much attention this year. The issues I opened haven’t been looked at. Ralph > On Apr 25, 2022, at 9:56 PM, Gary Gregory wrote: > > From my POV, regardless of the version label, the sooner the better for a > release out of develop, not that I want to take the time to RM ATM, just my > 2c. > > Gary > > On Mon, Apr 25, 2022, 15:15 Piotr P. Karwasz > wrote: > >> Hi Gary, >> >> I was just sorting my Jira issues in preparation for 2.17.3, although I >> must agree with you, that calling it 2.17.3 is a little bit of a stretch. I >> count 5-6 "bugs" that actually introduced new features. >> >> On the other hand I would really like to see a release somewhere in June, >> so I can move the issues concerning SLF4J 2.0 to 2.19.0 (I don't think Ceki >> is going to release a beta soon anyway) and submit a PR for LOG4J2-3483 >> (support for Apache Extras RollingFileAppender) by mid-May. >> >> Piotr >> >> On Mon, 25 Apr 2022 at 20:33, Gary Gregory wrote: >> >>> Hi all, >>> >>> I don't think we should have a 2.17.3 as there are already new features >> in >>> develop since 2.17.2. >>> >>> Gary >>> >>
Re: 2.17.3 vs 2.18.0
>From my POV, regardless of the version label, the sooner the better for a release out of develop, not that I want to take the time to RM ATM, just my 2c. Gary On Mon, Apr 25, 2022, 15:15 Piotr P. Karwasz wrote: > Hi Gary, > > I was just sorting my Jira issues in preparation for 2.17.3, although I > must agree with you, that calling it 2.17.3 is a little bit of a stretch. I > count 5-6 "bugs" that actually introduced new features. > > On the other hand I would really like to see a release somewhere in June, > so I can move the issues concerning SLF4J 2.0 to 2.19.0 (I don't think Ceki > is going to release a beta soon anyway) and submit a PR for LOG4J2-3483 > (support for Apache Extras RollingFileAppender) by mid-May. > > Piotr > > On Mon, 25 Apr 2022 at 20:33, Gary Gregory wrote: > > > Hi all, > > > > I don't think we should have a 2.17.3 as there are already new features > in > > develop since 2.17.2. > > > > Gary > > >
Upgradable dependencies
Hello, Dependabot has reached the maximum number of PRs allowed by its configuration, so I believe it is spring cleaning time. Some actions are no brainers: * `javax.servlet-api` (https://github.com/apache/logging-log4j2/pull/803) should stay at 3.0, since we don't use features from higher version, * `cassandra-all` 2.2.8 (https://github.com/apache/logging-log4j2/pull/817) is unsupported and has 2 vulnerabilities. We should switch to 3.0.26, although this requires some code changes. Do we need to do it before 2.18.0? Other 'bumps' require IMHO some discussion: * `org.apache.felix.framework` is used only for testing. Should we switch to a newer version? * `maven-bundle-plugin`: documentation seems to be stuck at 4.2.1, while the implementation reached 5.1.4. Do we need to upgrade? Piotr
Re: 2.17.3 vs 2.18.0
Hi Gary, I was just sorting my Jira issues in preparation for 2.17.3, although I must agree with you, that calling it 2.17.3 is a little bit of a stretch. I count 5-6 "bugs" that actually introduced new features. On the other hand I would really like to see a release somewhere in June, so I can move the issues concerning SLF4J 2.0 to 2.19.0 (I don't think Ceki is going to release a beta soon anyway) and submit a PR for LOG4J2-3483 (support for Apache Extras RollingFileAppender) by mid-May. Piotr On Mon, 25 Apr 2022 at 20:33, Gary Gregory wrote: > Hi all, > > I don't think we should have a 2.17.3 as there are already new features in > develop since 2.17.2. > > Gary >
2.17.3 vs 2.18.0
Hi all, I don't think we should have a 2.17.3 as there are already new features in develop since 2.17.2. Gary
Re: [VOTE] Release log4cxx 0.13.0
Adding my +1 With that the release passes with binding +1 votes from Remko, Matt, and me, and +1 votes from Stephen and Thorsten. -Robert Middleton On Sun, Apr 24, 2022 at 5:50 PM Matt Sicker wrote: > > +1 > > Notes: > > * NOTICE file needs an updated copyright > — > Matt Sicker > > > On Apr 17, 2022, at 02:21, Stephen Webb wrote: > > > > +1 > > > > I tested 0.13.0 on Ubuntu and Windows - all OK > > > > On Sat, Apr 16, 2022 at 7:47 PM Thorsten Schöning > > wrote: > > > >> Guten Tag Robert Middleton, > >> am Samstag, 16. April 2022 um 03:00 schrieben Sie: > >> > >>> This is a vote to release log4cxx 0.13.0. > >> > >> +1 > >> > >> Mit freundlichen Grüßen > >> > >> Thorsten Schöning > >> > >> -- > >> AM-SoFT IT-Service - Bitstore Hameln GmbH > >> Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK > >> > >> E-Mail: thorsten.schoen...@am-soft.de > >> Web:http://www.AM-SoFT.de/ > >> > >> Tel: 05151- 9468- 0 > >> Tel: 05151- 9468-55 > >> Fax: 05151- 9468-88 > >> Mobil: 0178-8 9468-04 > >> > >> AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 > >> Hameln > >> AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska > >> > >> > >> Für Rückfragen stehe ich Ihnen jederzeit zur Verfügung. > >> > >> Mit freundlichen Grüßen, > >> > >> Thorsten Schöning > >> > >> > >> Telefon: +49 (0)515 94 68 - 0 > >> Fax: > >> E-Mail: tschoen...@am-soft.de > >> > >> AM-Soft IT-Service - Bitstore Hameln GmbH > >> Brandenburger Straße 7c > >> 31789 Hameln > >> > >> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > >> Informationen und ist ausschliesslich für den Adressaten bestimmt. > >> Jeglicher Zugriff auf diese E-Mail durch andere Personen als den Adressaten > >> ist untersagt. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > >> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > >> vernichten Sie diese E-Mail. Sollten Sie nicht der für diese E-Mail > >> bestimmte Adressat sein, ist Ihnen jede Veröffentlichung, Vervielfältigung > >> oder Weitergabe wie auch das Ergreifen oder Unterlassen von Massnahmen im > >> Vertrauen auf erlangte Information untersagt. > >> > >> This e-mail may contain confidential and/or privileged information and is > >> intended solely for the addressee. Access to this email by anyone else is > >> unauthorized. If you are not the intended recipient (or have received this > >> e-mail in error) please notify the sender immediately and destroy this > >> e-mail. If you are not the intended recipient, any disclosure, copying, > >> distribution or any action taken or omitted to be taken in reliance on it, > >> is prohibited and may be unlawful. > >> > >> Hinweise zum Datenschutz: bitstore.group/datenschutz > >> > >> > >> > >> >
