Thanks Volkan -- Matt, I believe release 1.4.0 is ready for a vote.
* ASF staging site:
https://logging.staged.apache.org/log4j/kotlin/latest/#release-notes-1-4-0
(from branch
https://github.com/apache/logging-log4j-kotlin/commits/asf-staging/)
* Signed distribution and checksums:
https://dist.a
Thanks for the prompt action. 🙏
I will review the PR.
Please keep in mind that you don't have sufficient rights to complete a
release. A PMC member should volunteer as an RM (Release Manager), who, in
your case, is Matt, I presume. That is, you can perform the git chores, but
it is Matt who should
Thanks for the feedback Volkan. The PR with all of these changes is:
https://github.com/apache/logging-log4j-kotlin/pull/56
Regards,
Raman
On Thu, Dec 7, 2023 at 5:54 AM Volkan Yazıcı wrote:
> Raman, Matt, great that you want to release the next version of the Log4j
> Kotlin! Thanks for your t
Thanks for the info! I don’t think you’re being pedantic here; the uniform
release process is very important to keeping all our components healthy.
> On Dec 7, 2023, at 4:54 AM, Volkan Yazıcı wrote:
>
> Raman, Matt, great that you want to release the next version of the Log4j
> Kotlin! Thanks f
Raman, Matt, great that you want to release the next version of the Log4j
Kotlin! Thanks for your time and effort.
I see that you forked the `release/1.3.1` branch from the `rel/1.3.0` tag,
though this misses some minor, but important changes (e.g., SBOM & VDR!)
from `main`. I suggest we fork fro
