ppkarwasz commented on PR #3341: URL: https://github.com/apache/logging-log4j2/pull/3341#issuecomment-3626545300
I added more precise release instructions in apache/logging-parent#453, but lifecycle documentation can’t really be automated today. Lifecycle events (`endOfDevelopment`, `endOfSupport`, `endOfLife`) depend on PMC policy decisions and must be applied manually by the release manager. ATR will simplify this in the future (see apache/tooling-trusted-releases#183), so adding project-specific automation now doesn’t seem worthwhile. The Log4j release automation you built has saved days of work across a dozen releases and is finally paying off. Automating lifecycle information would offer far smaller benefits. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
