Adding my +1 here.
With that, the release passes with +1 votes from Remko Popma, Matt
Sicker, and Robert Middleton.
I shall proceed with the release.
-Robert Middleton
On Sun, Jun 6, 2021 at 3:22 PM Matt Sicker wrote:
>
> Nits (not blockers, but useful to fix for next release):
> * Source arch
Nits (not blockers, but useful to fix for next release):
* Source archive should be created by adding the option
--prefix=apache-chainsaw-2.1.0/ so that the archives are inside a
directory. As is, they don't have a containing directory which can be
unexpected.
+1
Signatures good, built and tested
+1
On Sun, Jun 6, 2021 at 9:36 AM Robert Middleton
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.
>
> This vote supersedes the original vote
>
> Differences from RC1:
> * Adde
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.
This vote supersedes the original vote
Differences from RC1:
* Added source archive. Note that this is created with 'git archive'
* Updated c
I'm working on that now. I'm just fixing the copyright date in the
NOTICE file and making sure that the sign-artifacts will sign the
source archive, so just a few minor changes.
-Robert Middleton
On Sat, Jun 5, 2021 at 8:11 PM Ralph Goers wrote:
>
> Is something going to be done to address the
Is something going to be done to address the need for a source archive? It
should be possible to create one based on the release work that has already
been performed.
Ralph
> On Jun 3, 2021, at 7:51 AM, Matt Sicker wrote:
>
> Minimal source releases can be made by using git archive on the tag
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 wrote:
> Unfortunately, without a source zip or gz there is no release to approve.
>
> Ralph
>
> > On Jun 1,
Unfortunately, without a source zip or gz there is no release to approve.
Ralph
> On Jun 1, 2021, at 6:58 PM, Robert Middleton 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
I was just going off of what was in the SVN develop repo before -
there wasn't a sources file in there, so I didn't add one. That being
said, the only thing that is generated at the moment is a sources.jar
with the sources, but that's probably not the correct thing to do for
the sources. It looks
On Tue, Jun 1, 2021 at 11:37 PM Matt Sicker wrote:
>
> The NOTICE file still has a copyright from 2007, but that was already
> a problem in the previous release, so that can be fixed in another
> release. Also, it looks like you didn't commit the source archives to
> svn yet?
As a reminder, Apach
The NOTICE file still has a copyright from 2007, but that was already
a problem in the previous release, so that can be fixed in another
release. Also, it looks like you didn't commit the source archives to
svn yet?
On Tue, 1 Jun 2021 at 20:58, Robert Middleton wrote:
>
> This vote is to release
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 vot
12 matches
Mail list logo