Thanks Matt I was trying to use GitHub's release feature to create a draft release to present binaries including signing and hashing, and needed a tag to work against; however, I think that this process won't work anyway, because I'm not 100% sure on the visibility of a draft release. I've deleted the tag, and attempted to create a draft release -- please could you verify if you can view the draft release? If so (and you can view the binaries), I can start a vote for 2.0.10. I also added the updated site to the `asf-staging` branch of the logging repo, so if the release is verifyable at GitHub, I'm ready to request a vote. The only problem is that I've signed the release artifacts -- last time, I believe Ralph did, and I'm not sure if my gpg key is acceptable.
-d On 2020/09/06 20:12:46, Matt Sicker <boa...@gmail.com> wrote: It's not a good idea to use rel/ tags until after a release vote since those tags are immutable. If you want to put them in rel/, they'll need an -rc1 type suffix to distinguish from the resulting release. On Sun, 6 Sep 2020 at 13:10, wrote: > > This is an automated email from the ASF dual-hosted git repository. > > davydm pushed a change to tag rel/2.0.10 > in repository https://gitbox.apache.org/repos/asf/logging-log4net.git. > > > at 2105ec8 (commit) > No new revisions were added by this update. > -- Matt Sicker
