date:20221205

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

2022-12-05 Thread Alex Herbert

Thanks for the notes. I'm fine with exposing the clear() method if it
is intentional.

+1.

Alex

On Mon, 5 Dec 2022 at 18:37, Gary Gregory  wrote:
>
> Hi Alex,
>
> Thank you for the thorough review. Please find my notes below.
>
> On Mon, Dec 5, 2022, 09:31 Alex Herbert  wrote:
>
> > Verified the source signatures and hashes.
> >
> > Built from the tag using: mvn install site
> >
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: /usr/local/apache-maven-3
> > Java version: 1.8.0_352, vendor: Private Build, runtime:
> > /usr/lib/jvm/java-8-openjdk-amd64/jre
> > Default locale: en_GB, platform encoding: UTF-8
> > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> > "unix"
> >
> > 3 javadocs warnings for this.
> >
>
> Yes, I get 100 Javadoc warnings with 'mvn javadoc:javadoc' which I think
> Javadoc limits to 100 by default.
> I've cleaned up and filled in a lot of Javadocs for this and past releases,
> but this is a large ongoing task that should not block a release IMO since
> the current docs are now better.
>
>
> > Build from the src tar.gz using the default goal and:
> >
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: /usr/local/apache-maven-3
> > Java version: 1.8.0_352, vendor: Private Build, runtime:
> > /usr/lib/jvm/java-8-openjdk-amd64/jre
> > Default locale: en_GB, platform encoding: UTF-8
> > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> > "unix"
> >
> > 3 javadocs warnings for this too.
> >
> > Build from the src zip using the default goal and:
> >
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: /usr/local/apache-maven-3
> > Java version: 17.0.4.1, vendor: Oracle Corporation, runtime:
> > /usr/lib/jvm/jdk-17.0.4.1
> > Default locale: en_GB, platform encoding: UTF-8
> > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> > "unix"
> >
> > Lots of javadoc warnings for this. JDK 17 is obviously a lot stricter
> > on public members missing comments.
> >
> > Release notes link for the changes report is missing a '/':
> >
>
> I can fix that post-release (
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.7.0-RC1/RELEASE-NOTES.txt
> )
>
>
> >
> > https://commons.apache.org/proper/commons-bcelchanges-report.html
> >
> > Checked the site:
> >
> > Most reports seem OK.
> >
> > Test coverage is improving. Up to 63% since the last release at 50%.
> >
> > JApiCmp: All new classes methods have the correct tag @since 6.7.0.
> >
> > Trivial: The org.apache.bcel.classfile.MethodParameter now implements
> > Node. This is new but cannot be added to the @since tag. It could be
> > added in the class header javadoc.
> >
>
> To do post-release IMO.
>
>
> >
> > Issue: The org.apache.bcel.verifier.VerfierFactory has a method @since
> > 6.6.2 changed from package-private to public. I believe this is a
> > testing method and has only been exposed as public for use in the test
> > case: org.apache.bcel.AbstractTestCase. It is not called within the
> > main source package.
> >
> > For situations like this where the leak into the public has happened
> > for testing it is possible to add a static helper class to the package
> > in the test src that calls the package-private method on the class,
> > e.g.
> >
> > package org.apache.bcel.verifier;
> >
> > public class VerifyHelper {
> > public static void clearVerifierFactory() {
> > VerifierFactory.clear();
> > }
> > }
> >
> > So can we be sure that exposing the clear() method into the public API
> > is acceptable. The javadoc states that the purpose of VerifierFactory
> > is to create singletons. So exposing the clear() method will prevent
> > this purpose as singletons will be cleared and classes recreated.
> > Thoughts on this?
> >
>
> Yes, this was intentional: It turns out that we have a few classes with
> global/static caches and there should be a way to clear a cache for
> long-running apps or apps that load and unload different data.
>
> TY!,
> Gary
>
>
> >
> >
> > Alex
> >
> > On Sun, 4 Dec 2022 at 20:45, Gary Gregory  wrote:
> > >
> > > PMC members, please take a look.
> > >
> > > Gary
> > >
> > > On Sat, Dec 3, 2022, 07:51 Gary Gregory  wrote:
> > >
> > > > Please take the time to review and vote on this RC.
> > > >
> > > > Gary
> > > >
> > > > On Fri, Dec 2, 2022 at 8:54 AM Gary Gregory 
> > > > wrote:
> > > > >
> > > > > ping ;-)
> > > > >
> > > > > On Mon, Nov 28, 2022 at 2:12 PM Bruno Kinoshita 
> > > > wrote:
> > > > > >
> > > > > >[x] +1 Release these artifacts
> > > > > >
> > > > > > Building OK from tag with:
> > > > > >
> > > > > > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> > > > > > Maven home: /opt/apache-maven-3.8.5
> > > > > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > > > > /usr/lib/jvm/java-17-openjdk-amd64
> > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > OS name: "linux", version:

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

2022-12-05 Thread Gary Gregory

Hi Alex,

Thank you for the thorough review. Please find my notes below.

On Mon, Dec 5, 2022, 09:31 Alex Herbert  wrote:

> Verified the source signatures and hashes.
>
> Built from the tag using: mvn install site
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 1.8.0_352, vendor: Private Build, runtime:
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> "unix"
>
> 3 javadocs warnings for this.
>

Yes, I get 100 Javadoc warnings with 'mvn javadoc:javadoc' which I think
Javadoc limits to 100 by default.
I've cleaned up and filled in a lot of Javadocs for this and past releases,
but this is a large ongoing task that should not block a release IMO since
the current docs are now better.


> Build from the src tar.gz using the default goal and:
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 1.8.0_352, vendor: Private Build, runtime:
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> "unix"
>
> 3 javadocs warnings for this too.
>
> Build from the src zip using the default goal and:
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 17.0.4.1, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/jdk-17.0.4.1
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family:
> "unix"
>
> Lots of javadoc warnings for this. JDK 17 is obviously a lot stricter
> on public members missing comments.
>
> Release notes link for the changes report is missing a '/':
>

I can fix that post-release (
https://dist.apache.org/repos/dist/dev/commons/bcel/6.7.0-RC1/RELEASE-NOTES.txt
)


>
> https://commons.apache.org/proper/commons-bcelchanges-report.html
>
> Checked the site:
>
> Most reports seem OK.
>
> Test coverage is improving. Up to 63% since the last release at 50%.
>
> JApiCmp: All new classes methods have the correct tag @since 6.7.0.
>
> Trivial: The org.apache.bcel.classfile.MethodParameter now implements
> Node. This is new but cannot be added to the @since tag. It could be
> added in the class header javadoc.
>

To do post-release IMO.


>
> Issue: The org.apache.bcel.verifier.VerfierFactory has a method @since
> 6.6.2 changed from package-private to public. I believe this is a
> testing method and has only been exposed as public for use in the test
> case: org.apache.bcel.AbstractTestCase. It is not called within the
> main source package.
>
> For situations like this where the leak into the public has happened
> for testing it is possible to add a static helper class to the package
> in the test src that calls the package-private method on the class,
> e.g.
>
> package org.apache.bcel.verifier;
>
> public class VerifyHelper {
> public static void clearVerifierFactory() {
> VerifierFactory.clear();
> }
> }
>
> So can we be sure that exposing the clear() method into the public API
> is acceptable. The javadoc states that the purpose of VerifierFactory
> is to create singletons. So exposing the clear() method will prevent
> this purpose as singletons will be cleared and classes recreated.
> Thoughts on this?
>

Yes, this was intentional: It turns out that we have a few classes with
global/static caches and there should be a way to clear a cache for
long-running apps or apps that load and unload different data.

TY!,
Gary


>
>
> Alex
>
> On Sun, 4 Dec 2022 at 20:45, Gary Gregory  wrote:
> >
> > PMC members, please take a look.
> >
> > Gary
> >
> > On Sat, Dec 3, 2022, 07:51 Gary Gregory  wrote:
> >
> > > Please take the time to review and vote on this RC.
> > >
> > > Gary
> > >
> > > On Fri, Dec 2, 2022 at 8:54 AM Gary Gregory 
> > > wrote:
> > > >
> > > > ping ;-)
> > > >
> > > > On Mon, Nov 28, 2022 at 2:12 PM Bruno Kinoshita 
> > > wrote:
> > > > >
> > > > >[x] +1 Release these artifacts
> > > > >
> > > > > Building OK from tag with:
> > > > >
> > > > > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> > > > > Maven home: /opt/apache-maven-3.8.5
> > > > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > > > /usr/lib/jvm/java-17-openjdk-amd64
> > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > OS name: "linux", version: "5.15.0-53-generic", arch: "amd64",
> family:
> > > > > "unix"
> > > > >
> > > > > Site reports look OK too.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Bruno
> > > > >
> > > > > On Mon, 28 Nov 2022 at 18:13, Gary Gregory  >
> > > wrote:
> > > > >
> > > > > > We have fixed a few bugs and added some enhancements since Apache
> > > > > > Commons BCEL 6.6.1 was released, so I would like to release
> Apache
> > > > > > Commons BCEL 6.7.0.
> >

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

2022-12-05 Thread Alex Herbert

On Mon, 5 Dec 2022 at 16:57, Bruno Kinoshita  wrote:
>
>[x] +1 Release these artifacts
>
> Tested with
>
> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> Maven home: /opt/apache-maven-3.8.5
> Java version: 17.0.5, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-56-generic", arch: "amd64", family:
> "unix"
>
> From tag, using mvn clean test install site.
>
> Reports look OK, checked NOTICE, LICENSE, and RELEASE-NOTES files, found no
> issues. Signatures also look OK in the dist area. Inspected some archives
> from the dist area and all look OK.
>
> Only odd thing was a CONTRIBUTING.md in the dist area, but I believe that
> will be fixed during the final release (not a big issue).

Yes, and I did wonder why it was there.

This file is present in rng and geometry in the dist area. The release
process has (blindly) copied those projects.

However, it is not there for numbers which shares a similar release
process, or other commons projects like lang and text.

I can remove the files from the relevant projects, and update their
release notes so it does not get put back.

Alex

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

2022-12-05 Thread Bruno Kinoshita

   [x] +1 Release these artifacts

Tested with

Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.5, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-56-generic", arch: "amd64", family:
"unix"

>From tag, using mvn clean test install site.

Reports look OK, checked NOTICE, LICENSE, and RELEASE-NOTES files, found no
issues. Signatures also look OK in the dist area. Inspected some archives
from the dist area and all look OK.

Only odd thing was a CONTRIBUTING.md in the dist area, but I believe that
will be fixed during the final release (not a big issue).

Thank you!

Bruno

On Thu, 1 Dec 2022 at 18:32, Alex Herbert  wrote:

> I would like to release Apache Commons Statistics 1.0.
>
> Apache Commons Statistics 1.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/statistics/1.0-RC1
> (svn revision 58393)
>
> The Git tag commons-statistics-1.0-RC1 commit for this RC is
> commons-statistics-1.0-RC1 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-statistics.git;a=commit;h=commons-statistics-1.0-RC1
>
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-statistics.git
> --branch
> 
> commons-statistics-1.0-RC1 commons-statistics-1.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1609/org/apache/commons/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Thu Dec 01 16:46:47 GMT 2022
>
> commons-statistics-1.0-bin.tar.gz=6a3cf6768e6d8c28992566811efa176bad78c74a587ef5420748fb913ece7dec85c459fd7dd72e0fc53a35b18d1b8b1a78e93a8a029f4ce78adc5038b3a6216f
>
> commons-statistics-1.0-bin.zip=28d0475cbf638c9776f62991f5428abebc43ee61de94e1cf4d92ea90a9034fff08d6af11297194ac70ad045c9955a04b8bc20729e02d6797a7a3a1e786ecd1b6
>
> commons-statistics-1.0-src.tar.gz=008484a1b0302d6fcbd221b21cfc78fb47b401749991a6ecf951996a86c86a8595f51aaa9e125ca611cc236d7b5107e0a2ed85d55e39420afade475f6e49a012
>
> commons-statistics-1.0-src.zip=c012c44d02a6210beb53d7ca5efd577704cdf34851af862d301c454683eecebe716ef46932d843292dc772147d068b142126dd5450623e640fd2c550f979ad76
>
>
> I have tested this with 'mvn clean install site site:stage -Pexamples'
> using:
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 1.8.0_352, vendor: Private Build, runtime:
> /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-197-generic", arch: "amd64", family:
> "unix"
>
> Release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/statistics/1.0-RC1/RELEASE-NOTES.txt
>
> Site:
> https://home.apache.org/~aherbert/commons-statistics-1.0-RC1-site/
> (note some *relative* links are broken and the 1.0 directories are
> not yet created - these will be OK once the site is deployed.)
>
> No JApiCmp Report for a 1.0 release
>
> RAT Report:
>
> https://home.apache.org/~aherbert/commons-statistics-1.0-RC1-site/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thank you,
>
> Alex Herbert,
> Release Manager (using key BC87A3FD0A54480F0BADBEBD21939FF0CA2A6567)
> --
>
> The following is intended as a helper and refresher for reviewers.
>
> Validating a release candidate
> ==
>
> These guidelines are NOT complete.
>
> Requirements: Git, Java, Maven.
>
> You can validate a release from a release candidate (RC) tag as follows.
>
> 1) Clone and checkout the RC tag
>
> git clone https://gitbox.apache.org/repos/asf/commons-statistics.git
> --branch
> 
> commons-statistics-1.0-RC1 commons-statistics-1.0-RC1
> cd commons-statistics-1.0-RC1
>
> 1b) Download and unpack the source archive from:
>
> https://dist.apache.org/repos/dist/dev/commons/statistics/1.0-RC1/source/
>
> 2) Check Apache licenses
>
> This step is not required if the site includes a RAT report page which
> you then must check.
>
> mvn apache-rat:check
>
> 3) Build the package
>
> mvn -V clean package
>
> You can record the Maven and Java version produced by -V in your VOTE
> reply.
> To gather OS information from a command line:
> Windows: ver
> Linux: uname -a
>
> 4) Build the site for a multi-module project
>
> mvn site site:stage -Pexamples
> Check the site reports in:
> - Windows: target\staging\index.html
> - Linux: target/staging/index.html
>
> Note that modules can be accessed using

Re: Any plans to release DBUtils anytime soon?

2022-12-05 Thread Carl Hall

Hi, all! I'm working through the PR backlog and correcting build errors.
Once I get things settled, I'll return to the 2.0 release from a couple of
years ago to cancel & restart that motion.

On Tue, Nov 8, 2022 at 12:30 PM Gary Gregory  wrote:

> And for the curious my plan for a release train is: BCEL, Net, Crypto, CSV,
> Pool, DBCP, Configuration.
>
> Gary
>
> On Tue, Nov 8, 2022, 12:27 Gary Gregory  wrote:
>
> > I can only give the usual response: We are unpaid volunteers with limited
> > time and priorities that may not align with what you might be
> specifically
> > looking for.
> >
> > Gary
> >
> > On Tue, Nov 8, 2022, 11:45 mkpaz  wrote:
> >
> >> Hello!
> >>
> >> It's been awhile since DBUtils last release in 2017. There was a lot of
> >> good work done. Could you please share why it's
> >> not getting updates. Any blocking issues?
> >>
> >> Mike.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

2022-12-05 Thread Alex Herbert

Verified the source signatures and hashes.

Built from the tag using: mvn install site

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/apache-maven-3
Java version: 1.8.0_352, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix"

3 javadocs warnings for this.

Build from the src tar.gz using the default goal and:

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/apache-maven-3
Java version: 1.8.0_352, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix"

3 javadocs warnings for this too.

Build from the src zip using the default goal and:

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/apache-maven-3
Java version: 17.0.4.1, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/jdk-17.0.4.1
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix"

Lots of javadoc warnings for this. JDK 17 is obviously a lot stricter
on public members missing comments.

Release notes link for the changes report is missing a '/':

https://commons.apache.org/proper/commons-bcelchanges-report.html

Checked the site:

Most reports seem OK.

Test coverage is improving. Up to 63% since the last release at 50%.

JApiCmp: All new classes methods have the correct tag @since 6.7.0.

Trivial: The org.apache.bcel.classfile.MethodParameter now implements
Node. This is new but cannot be added to the @since tag. It could be
added in the class header javadoc.

Issue: The org.apache.bcel.verifier.VerfierFactory has a method @since
6.6.2 changed from package-private to public. I believe this is a
testing method and has only been exposed as public for use in the test
case: org.apache.bcel.AbstractTestCase. It is not called within the
main source package.

For situations like this where the leak into the public has happened
for testing it is possible to add a static helper class to the package
in the test src that calls the package-private method on the class,
e.g.

package org.apache.bcel.verifier;

public class VerifyHelper {
public static void clearVerifierFactory() {
VerifierFactory.clear();
}
}

So can we be sure that exposing the clear() method into the public API
is acceptable. The javadoc states that the purpose of VerifierFactory
is to create singletons. So exposing the clear() method will prevent
this purpose as singletons will be cleared and classes recreated.
Thoughts on this?

Alex

On Sun, 4 Dec 2022 at 20:45, Gary Gregory  wrote:
>
> PMC members, please take a look.
>
> Gary
>
> On Sat, Dec 3, 2022, 07:51 Gary Gregory  wrote:
>
> > Please take the time to review and vote on this RC.
> >
> > Gary
> >
> > On Fri, Dec 2, 2022 at 8:54 AM Gary Gregory 
> > wrote:
> > >
> > > ping ;-)
> > >
> > > On Mon, Nov 28, 2022 at 2:12 PM Bruno Kinoshita 
> > wrote:
> > > >
> > > >[x] +1 Release these artifacts
> > > >
> > > > Building OK from tag with:
> > > >
> > > > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> > > > Maven home: /opt/apache-maven-3.8.5
> > > > Java version: 17.0.5, vendor: Private Build, runtime:
> > > > /usr/lib/jvm/java-17-openjdk-amd64
> > > > Default locale: en_US, platform encoding: UTF-8
> > > > OS name: "linux", version: "5.15.0-53-generic", arch: "amd64", family:
> > > > "unix"
> > > >
> > > > Site reports look OK too.
> > > >
> > > > Thanks!
> > > >
> > > > Bruno
> > > >
> > > > On Mon, 28 Nov 2022 at 18:13, Gary Gregory 
> > wrote:
> > > >
> > > > > We have fixed a few bugs and added some enhancements since Apache
> > > > > Commons BCEL 6.6.1 was released, so I would like to release Apache
> > > > > Commons BCEL 6.7.0.
> > > > >
> > > > > Apache Commons BCEL 6.7.0 RC1 is available for review here:
> > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.7.0-RC1
> > (svn
> > > > > revision 58280)
> > > > >
> > > > > The Git tag commons-bcel-6.7.0-RC1 commit for this RC is
> > > > > 6fc2135e6b1dca14716287e72bf813cb209bdbbd which you can browse here:
> > > > >
> > > > >
> > https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=6fc2135e6b1dca14716287e72bf813cb209bdbbd
> > > > > You may checkout this tag using:
> > > > > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> > > > > --branch <
> > https://gitbox.apache.org/repos/asf/commons-bcel.git--branch>
> > > > > commons-bcel-6.7.0-RC1 commons-bcel-6.7.0-RC1
> > > > >
> > > > > Maven artifacts are here:
> > > > >
> > > > >
> > https://repository.apache.org/content/repositories/orgapachecommons-1608/org/apache/bcel/bcel/6.7.0/
> > > > >
> > > > > These are the artifacts and their hashes:
> > > > >
> > > > > #Release SHA-512s
> > > > >

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

2022-12-05 Thread Alex Herbert

Can I have another PMC vote please.

Thank you.

Alex

On Mon, 5 Dec 2022 at 01:57, Gilles Sadowski  wrote:
>
> Le jeu. 1 déc. 2022 à 18:32, Alex Herbert  a écrit :
> >
> > I would like to release Apache Commons Statistics 1.0.
> >
> > Apache Commons Statistics 1.0 RC1 is available for review here:
> > https://dist.apache.org/repos/dist/dev/commons/statistics/1.0-RC1
> > (svn revision 58393)
> >
> > [...]
> >
>   [X] +1 Release these artifacts
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this release because...
> >
>
> Gilles
>
> > []
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

Re: Any plans to release DBUtils anytime soon?

Re: [VOTE] Release Apache Commons BCEL 6.7.0 based on RC1

Re: [VOTE] Release Apache Commons Statistics 1.0 based on RC1

7 matches

Site Navigation

Mail list logo

Footer information