Release notes, changelog and commits

arious channels. Specifically, I’d like to clarify our approach regarding the following: 1. **Release Notes** These are the curated summaries we write in `.release-notes.adoc.ftl` files. In my view, release notes are essential and should appear in all of the following: * Our website. * The VOT

[log4j] Links to issues in VOTE emails and release notes (Was: [VOTE] Release Apache Log4j `2.25.1` (RC1))

] Please note that the Apache Trusted Release (ATR) tool is currently > in alpha, and votes cast through ATR are not officially counted in the > release process. However, Apache committers are encouraged to try it out > and provide feedback using the following URL: > > https://

Re: Log4net: 2.0.9 release notes missing

I do not believe the site has been updated to reflect the release. I looked into it but couldn’t figure out how to build the site. Ralph > On Aug 24, 2020, at 6:38 AM, Dominik Psenner wrote: > > Hi > > People noticed that the release notes of 2.0.9 are missing while t

Log4net: 2.0.9 release notes missing

Hi People noticed that the release notes of 2.0.9 are missing while they should be documented here: http://logging.apache.org/log4net/release/release-notes.html Best regards -- Sent from my phone. Typos are a kind gift to anyone who happens to find them.

Re: Release notes

orm text > that describes the release. It should be edited as needed. Most > enhancements and fixes don’t need to be called out there. > >>> > >>> Ralph > >>> > >>>> On Jun 29, 2017, at 12:14 PM, Gary Gregory > wrote: > >>>>

Re: Release notes

release. It should be edited as needed. Most enhancements and >>> fixes don’t need to be called out there. >>> >>> Ralph >>> >>>> On Jun 29, 2017, at 12:14 PM, Gary Gregory wrote: >>>> >>>> Just documenting which file to u

Re: Release notes

documenting which file to update and that it gets appended... On Jun 29, 2017 12:11 PM, "Ralph Goers" wrote: Updating the release notes is already a step in the release process. Are you talking about a different wiki page? Ralph On Jun 29, 2017, at 10:33 AM, Gary Gregory wrote: Anoth

Re: Release notes

;> >> On Jun 29, 2017 12:11 PM, "Ralph Goers" wrote: >> >>> Updating the release notes is already a step in the release process. Are >>> you talking about a different wiki page? >>> >>> Ralph >>> >>>> On Jun 29,

Re: Release notes

to update and that it gets appended... > > On Jun 29, 2017 12:11 PM, "Ralph Goers" wrote: > >> Updating the release notes is already a step in the release process. Are >> you talking about a different wiki page? >> >> Ralph >> >>> On

Re: Release notes

Just documenting which file to update and that it gets appended... On Jun 29, 2017 12:11 PM, "Ralph Goers" wrote: > Updating the release notes is already a step in the release process. Are > you talking about a different wiki page? > > Ralph > > > On Jun 29,

Re: Release notes

Updating the release notes is already a step in the release process. Are you talking about a different wiki page? Ralph > On Jun 29, 2017, at 10:33 AM, Gary Gregory wrote: > > Another step in the wiki? > > Gary > > On Jun 29, 2017 08:42, "Mikael Ståldal" wrot

Re: Release notes

ut in this case I want something more which cannot be placed in >>> changes.xml. >>> >>> On 2017-06-29 14:37, Remko Popma wrote: >>> >>>> Release Notes = changes.xml, no? >>>> (Shameless plug) Every java main() method deserves http://pico

Re: Release notes

the announcement text. Ralph On Jun 29, 2017, at 6:02 AM, Mikael Ståldal wrote: Yes, but in this case I want something more which cannot be placed in changes.xml. On 2017-06-29 14:37, Remko Popma wrote: Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http

Re: Release notes

dal wrote: > > Yes, but in this case I want something more which cannot be placed in > changes.xml. > > On 2017-06-29 14:37, Remko Popma wrote: >> Release Notes = changes.xml, no? >> (Shameless plug) Every java main() method deserves http://picocli.info >>> On

Re: Release notes

Yes, but in this case I want something more which cannot be placed in changes.xml. On 2017-06-29 14:37, Remko Popma wrote: Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http://picocli.info On Jun 29, 2017, at 19:48, Mikael Ståldal wrote: Do we have

Re: Release notes

Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 29, 2017, at 19:48, Mikael Ståldal wrote: > > Do we have any place to prepare release notes for an upcoming release, before > actually making the release? &

Release notes

Do we have any place to prepare release notes for an upcoming release, before actually making the release? Removing SerializedLayout as default warrants a mentioning in the release notes for the 2.9 release, since it is a breaking change.