There seems to be an increased interest from users around making releases of various components in order to clean up their security checklists mandated from above. Since making releases is somewhat standardized here, would it make sense to create some sort of guide for volunteers who want releases to get involved and do the work? It would definitely be great to point to a link whenever someone comes in asking for commons-xyz to be released because it has an outdated dependency or some security scanner identified some issue that was fixed but unreleased.
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
