Minimal source releases can be made by using git archive on the tag and signing/hashing the file. Then commit those to the release candidate repo.
On Wed, Jun 2, 2021 at 23:22 Ralph Goers <ralph.go...@dslextreme.com> wrote: > Unfortunately, without a source zip or gz there is no release to approve. > > Ralph > > > On Jun 1, 2021, at 6:58 PM, Robert Middleton <rmiddle...@apache.org> > wrote: > > > > This vote is to release Apache Chainsaw 2.1.0. This fixes a few > > annoying issues with chainsaw and some other bugs, as well as updating > > some dependencies. > > > > Please download, test, and cast your votes on the log4j developers list. > > [] +1, release the artifacts > > [] -1, don't release because... > > > > This vote will remain open for 72 hours(or more if required). > > > > All votes are welcome and we encourage everyone to test the release, > > but only Logging PMC votes are “officially” counted. As always, at > > least 3 +1 votes and more positive than negative votes are required. > > > > Tag: > > For a new copy do "git clone > > https://github.com/apache/logging-chainsaw.git"; and then "git checkout > > tags/apache-chainsaw-2.1.0-RC1" > > > > Web site: https://logging.staged.apache.org/chainsaw/2.1.0/ > > > > Distribution archives: > https://dist.apache.org/repos/dist/dev/logging/chainsaw/ > > > > -Robert Middleton > > > > >
