rgoers commented on pull request #59: URL: https://github.com/apache/logging-log4net/pull/59#issuecomment-629685793
For the CLA see https://www.apache.org/licenses/contributor-agreements.html. In particular you need to fill out the ICLA and send it in according to the instructions. That is a prerequisite to becoming a committer. Jira was disabled for Log4Net when the project was moved to dormant status. We will request it be reactivated as part of the release. I see the build log but I can't tell if that is a valid release or not. Java development builds normally have -SNAPSHOT in the version and then the release does not. The main steps involved in a release are: 1. Tag the source with the release number. 2. Build the binaries from the tagged source (believe it or not, this step is actually optional) 3. Create an archive and/or zip of the source and binaries. 4. Sign and checksum the archives and zips. 5. Upload the archives, signatures, and checksums to the ASF dev distribution area (must be performed by a PMC member) 6. Send a Vote email on the release identifying the component, version and changes present in the release. Much of this will be used as the basis for the announcement email after the release is finished. 7. If the vote passes the archives, signatures and checksums are moved to the ASF release distribution area (must be performed by a PMC member). Updating the web site will most likely be part of the release process, but when and how it is updated is up to the team. However, the Apache announcement list requires that the download link be included near the front of the announcement email and it has to work. Sending an announcement to the announcement email is desirable but is not required. The email must be sent to the asf mail relay using an @apache.org email account. The announcement can also be posted to the ASF Logging blog. Finally, when the release passes you would want to upload the binaries to where users would most likely consume it, if that isn't from the ASF distribution directories. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
