You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by da...@apache.org on 2020/09/06 18:09:57 UTC
[logging-log4net] tag rel/2.0.10 created (now 2105ec8)
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.
Re: [logging-log4net] tag rel/2.0.10 created (now 2105ec8)
Posted by Davyd McColl <da...@gmail.com>.
Hi Matt
In that case, I can create an -rc1 release on GitHub; when everyone is happy, I can upload the accepted binaries to SVN so as not to upload too much junk (: I'll start a vote now (:
Thanks again for your help
-d
On 2020/09/06 20:43:16, Matt Sicker <bo...@gmail.com> wrote:
I don't think we've ever used the GitHub Releases feature here before,
though draft releases appear to be limited to being seen only by those
with write access to that. For making a release candidate, you'd
essentially be making a release for version X but adding -rc1 (or
-rc2, etc.) to the tag name to indicate the release candidate. Then in
the release vote, we can check out that tag (and any artifacts). For
uploading artifacts, you should be able to commit files to this svn
repo:
https://dist.apache.org/repos/dist/dev/logging/log4net/
It could be an interesting idea to figure out how to use the GitHub
Releases feature, though we'd have to make sure that the archives it
links to are the same ones that we vote to release.
As for signing, please use your gpg key. We've added it to the KEYS
file so that users can verify the release signature. The point of
signing it is to keep a secure supply chain from the release manager
(you in this case) to the end user.
[you = Davyd]
On Sun, 6 Sep 2020 at 13:33, Davyd McColl wrote:
>
> 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 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
--
Matt Sicker
Re: [logging-log4net] tag rel/2.0.10 created (now 2105ec8)
Posted by Matt Sicker <bo...@gmail.com>.
I don't think we've ever used the GitHub Releases feature here before,
though draft releases appear to be limited to being seen only by those
with write access to that. For making a release candidate, you'd
essentially be making a release for version X but adding -rc1 (or
-rc2, etc.) to the tag name to indicate the release candidate. Then in
the release vote, we can check out that tag (and any artifacts). For
uploading artifacts, you should be able to commit files to this svn
repo:
https://dist.apache.org/repos/dist/dev/logging/log4net/
It could be an interesting idea to figure out how to use the GitHub
Releases feature, though we'd have to make sure that the archives it
links to are the same ones that we vote to release.
As for signing, please use your gpg key. We've added it to the KEYS
file so that users can verify the release signature. The point of
signing it is to keep a secure supply chain from the release manager
(you in this case) to the end user.
[you = Davyd]
On Sun, 6 Sep 2020 at 13:33, Davyd McColl <da...@gmail.com> wrote:
>
> 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 <bo...@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
--
Matt Sicker <bo...@gmail.com>
Re: [logging-log4net] tag rel/2.0.10 created (now 2105ec8)
Posted by Davyd McColl <da...@gmail.com>.
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 <bo...@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
Re: [logging-log4net] tag rel/2.0.10 created (now 2105ec8)
Posted by Matt Sicker <bo...@gmail.com>.
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, <da...@apache.org> 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 <bo...@gmail.com>