Re: [VOTE] Release Apache Log4j Tools `0.9.0` RC2
Adding my +1. With that, the release passes with 3 binding +1 votes from Gary, Piotr, and me. I will continue the release process. On Thu, May 9, 2024 at 2:40 PM Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j Tools `0.9.0` RC2. > > Website: https://logging.staged.apache.org/log4j/tools-0.9.0 > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 485e1823cd6f8ae581071e938608db21126a7af5 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1285 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 48 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > == Review kit > > The minimum set of steps needed to review the uploaded distribution > files in the Subversion repository can be summarized as follows: > > # Check out the distribution > svn co https://dist.apache.org/repos/dist/dev/logging/log4j-tools/0.9.0 > && cd $_ > > # Verify checksums > shasum --check *.sha512 > > # Verify signatures > wget -O - https://downloads.apache.org/logging/KEYS | gpg --import > for sigFile in *.asc; do gpg --verify $sigFile; done > > # Verify reproduciblity > umask 0022 > unzip *-src.zip -d src > cd src > export > NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1285 > sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO > # If preferred, augment `mvnw` with `-DskipTests` to speed things up > > == Addendum > > Note that the vote period is 48 hours – 24 hours have already passed > since RC1 vote and there is only a single new commit added, see issue > #123. > > == Release notes > > This minor release contains small bug fixes and improvements. > > === Added > > * Add `skip` parameter to all Maven goals (#121) > * Support multiple index and type templates in the > `log4j-docgen:generate-documentation` configuration (#122) > * Add support for the `@PluginValue` annotation (#123) > > === Changed > > * Website is migrated to Antora (apache/logging-log4j2#2443) > > === Fixed > > * Fix handling of subclassed plugins in Log4j Docgen (#120) > > === Updated > > * Update `commons-io:commons-io` to version `2.16.1` (#114) > * Update `org.apache.logging:logging-parent` to version `11.0.0` (#115) > * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to > version `3.13.0` (#118) > * Update `org.codehaus.modello:modello-maven-plugin` to version `2.4.0` (#119) > * Update `org.xmlunit:xmlunit-assertj3` to version `2.10.0` (#116)
[ANNOUNCE] Apache Log4j Tools `0.9.0` released
Apache Log4j Tools team is pleased to announce the `0.9.0` release. This project provides tooling internally used by the Apache Log4j project. For further information (support, download, etc.) see the project website[1]. [1] https://logging.apache.org/log4j/tools == Release Notes This minor release contains small bug fixes and improvements. === Added * Add `skip` parameter to all Maven goals (#121) * Support multiple index and type templates in the `log4j-docgen:generate-documentation` configuration (#122) * Add support for the `@PluginValue` annotation. (#123) === Changed * Website is migrated to Antora (apache/logging-log4j2#2443) === Fixed * Fix handling of subclassed plugins in Log4j Docgen (#120) === Updated * Update `commons-io:commons-io` to version `2.16.1` (#114) * Update `org.apache.logging:logging-parent` to version `11.0.0` (#115) * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to version `3.13.0` (#118) * Update `org.codehaus.modello:modello-maven-plugin` to version `2.4.0` (#119) * Update `org.xmlunit:xmlunit-assertj3` to version `2.10.0` (#116)
Community over Code EU 2024: The countdown has started!
[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] We are very close to Community Over Code EU -- check out the amazing program and the special discounts that we have for you. Special discounts You still have the opportunity to secure your ticket for Community Over Code EU. Explore the various options available, including the regular pass, the committer and groups pass, and now introducing the one-day pass tailored for locals in Bratislava. We also have a special discount for you to attend both Community Over Code and Berlin Buzzwords from June 9th to 11th. Visit our website to find out more about this opportunity and contact te...@sg.com.mx to get the discount code. Take advantage of the discounts and register now! https://eu.communityovercode.org/tickets/ Check out the full program! This year Community Over Code Europe will bring to you three days of keynotes and sessions that cover topics of interest for ASF projects and the greater open source ecosystem including data engineering, performance engineering, search, Internet of Things (IoT) as well as sessions with tips and lessons learned on building a healthy open source community. Check out the program: https://eu.communityovercode.org/program/ Keynote speaker highlights for Community Over Code Europe include: * Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software Foundation, will discuss the Cyber Resiliency Act and its impact on open source (All your code belongs to Policy Makers, Politicians, and the Law). * Dr. Sherae Daniel will share the results of her study on the impact of self-promotion for open source software developers (To Toot or not to Toot, that is the question). * Asim Hussain, Executive Director of the Green Software Foundation will present a framework they have developed for quantifying the environmental impact of software (Doing for Sustainability what Open Source did for Software). * Ruth Ikegah will discuss the growth of the open source movement in Africa (From Local Roots to Global Impact: Building an Inclusive Open Source Community in Africa) * A discussion panel on EU policies and regulations affecting specialists working in Open Source Program Offices Additional activities * Poster sessions: We invite you to stop by our poster area and see if the ideas presented ignite a conversation within your team. * BOF time: Don't miss the opportunity to discuss in person with your open source colleagues on your shared interests. * Participants reception: At the end of the first day, we will have a reception at the event venue. All participants are welcome to attend! * Spontaneous talks: There is a dedicated room and social space for having spontaneous talks and sessions. Get ready to share with your peers. * Lighting talks: At the end of the event we will have the awaited Lighting talks, where every participant is welcome to share and enlighten us. Please remember: If you haven't applied for the visa, we will provide the necessary letter for the process. In the unfortunate case of a visa rejection, your ticket will be reimbursed. See you in Bratislava, Community Over Code EU Team
Author lines in documentation
Can we remove author lines in documentation pages? These lines are becoming crowded and somehow IntelliJ IDEA formats author lines badly (i.e. inserts a blank line before them and they end up in the text. Of course this doesn't need to be a PMC decision: when I reformat a page I'll remove the names of the authors that are OK with it (and I won't add mine ;-) ). Piotr
Re: Author lines in documentation
IMO, yes. I had them due to something needed them in the tooling we used to use. But like code, tags in the docs aren’t very valuable. Ralph > On May 14, 2024, at 8:00 AM, Piotr P. Karwasz wrote: > > Can we remove author lines in documentation pages? > > These lines are becoming crowded and somehow IntelliJ IDEA formats > author lines badly (i.e. inserts a blank line before them and they end > up in the text. > > Of course this doesn't need to be a PMC decision: when I reformat a > page I'll remove the names of the authors that are OK with it (and I > won't add mine ;-) ). > > Piotr
Re: Author lines in documentation
Agreed. The commit history is the best source of authorship anyway. Gary On Tue, May 14, 2024, 12:05 PM Ralph Goers wrote: > IMO, yes. I had them due to something needed them in the tooling we used > to use. But like code, tags in the docs aren’t very valuable. > > Ralph > > > On May 14, 2024, at 8:00 AM, Piotr P. Karwasz > wrote: > > > > Can we remove author lines in documentation pages? > > > > These lines are becoming crowded and somehow IntelliJ IDEA formats > > author lines badly (i.e. inserts a blank line before them and they end > > up in the text. > > > > Of course this doesn't need to be a PMC decision: when I reformat a > > page I'll remove the names of the authors that are OK with it (and I > > won't add mine ;-) ). > > > > Piotr > >
