[BCEL] PR to add accessors to model and unit tests, javadoc comments #183

[Gary Gregory]

Hi All & Mark R,
The https://github.com/apache/commons-bcel/pull/183 looks good to me.
I wanted to check with Mark R. and others if they see any issues.
TY!
Gary

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

[COLLECTIONS] documentation question

[Claude Warren]

Greetings,

I see that we support xml documents for documentation but does anyone know
if markdown is supported?  I have a number of markdown based documents that
would work well for the Bloom filter documentation, but translating to XML
will be a pain.

thanks,
Claude

Re: [COLLECTIONS] documentation question

[Phil Steitz]

On Sat, Jun 15, 2024 at 8:19 AM Claude Warren  wrote:

> Greetings,
>
> I see that we support xml documents for documentation but does anyone know
> if markdown is supported?  I have a number of markdown based documents that
> would work well for the Bloom filter documentation, but translating to XML
> will be a pain.
>

I know in the past some sites have used the now archaic apt format along
with the similarly ancient xdoc that most sites use.  I think the maven
site plugin allows you to combine content from different formats and
markdown is now a supported format, so this should not be a problem.  I
don't think you need to transform all of the site content to do that, but I
doubt anyone would complain - and many would be thankful - if you did.  See
[1].

Phil
[1]
https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html


>
> thanks,
> Claude
>

Re: [DRAFT] June Report to the Board

[Phil Steitz]

Thanks, Gary

Phil

On Wed, Jun 12, 2024 at 10:37 AM Gary D. Gregory 
wrote:

> I've edited the sections commented on as:
>
> ## Project Activity:
> Many releases of our components:
> CONFIGURATION-2.11.0 was released on 2024-06-10.
> NET-3.11.1 was released on 2024-06-10.
> PARENT-71 was released on 2024-06-10.
> JEXL-3.4.0 was released on 2024-06-06.
> NET-3.11.0 was released on 2024-05-31.
> VALIDATOR-1.9.0 was released on 2024-05-28.
> JCS-3.2.1 was released on 2024-05-27.
> DAEMON-1.4.0 was released on 2024-05-24.
> CLI-1.8.0 was released on 2024-05-23.
> COMPRESS-1.26.2 was released on 2024-05-23.
> LOGGING-1.3.2 was released on 2024-05-15.
> PARENT-70 was released on 2024-05-15.
> CSV-1.11.0 was released on 2024-05-02.
> RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> CLI-1.7.0 was released on 2024-04-18.
> IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> TEXT-1.12.0 was released on 2024-04-16.
> BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> IO-2.16.1 was released on 2024-04-08.
> COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> PARENT-69 was released on 2024-04-01.
> IO-2.16.0 was released on 2024-03-28.
> LOGGING-1.3.1 was released on 2024-03-24.
> PARENT-68 was released on 2024-03-23.
> CONFIGURATION-2.10.1 was released on 2024-03-20.
> CONFIGURATION-2.10.0 was released on 2024-03-13.
>
> ## Community Health:
> We welcomed Claude Warren as our latest PMC member. Mailing list activity
> has
> increased mostly due to GitHub automated emails. Most if not all of our
> growth
> in contributions are coming in through GitHub pull requests. GitHub PRs
> with
> our use of GitHub continuous integration builds provide
> validation of PRs and the existing code base. The flip side is that the
> increase in GitHub usage is matched by a decrease in Jira usage.
>
> Gary
>
> On 2024/06/12 14:17:50 Gilles Sadowski wrote:
> > Hi.
> >
> > Le mer. 12 juin 2024 à 15:45, Gary D. Gregory  a
> écrit :
> > >
> > > Hello All,
> > >
> > > Here is the draft of our board report for June I plan on submitting in
> a day or so, feedback is welcome.
> > >
> > > ## Description:
> > > The mission of Apache Commons is the creation and maintenance of Java
> focused
> > > reusable libraries and components
> > >
> > > ## Project Status:
> > > Current project status: Ongoing with moderate activity.
> > > Issues for the board: none.
> > >
> > > ## Membership Data:
> > > Apache Commons was founded 2007-06-19 (17 years ago)
> > > There are currently 149 committers and 44 PMC members in this project.
> > > The Committer-to-PMC ratio is roughly 5:2.
> > >
> > > Community changes, past quarter:
> > > - Claude Warren was added to the PMC on 2024-03-22
> > > - No new committers. Last addition was Claude Warren on 2022-02-01.
> > >
> > > ## Project Activity:
> > > Many releases of our components:
> > > CONFIGUATION-2.11.0 was released on 2024-06-10.
> > > NET-3.11.1 was released on 2024-06-10.
> > > PARENT-71 was released on 2024-06-10.
> > > JEXL-3.4.0 was released on 2024-06-06.
> > > NET-3.11.0 was released on 2024-05-31.
> > > VALIDATOR-1.9.0 was released on 2024-05-28.
> > > JCS-3.2.1 was released on 2024-05-27.
> > > DAEMON-1.4.0 was released on 2024-05-24.
> > > CLI-1.8.0 was released on 2024-05-23.
> > > COMPRESS-1.26.2 was released on 2024-05-23.
> > > LOGGING-1.3.2 was released on 2024-05-15.
> > > PARENT-70 was released on 2024-05-15.
> > > CSV-1.11.0 was released on 2024-05-02.
> > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> > > CLI-1.7.0 was released on 2024-04-18.
> > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> > > TEXT-1.12.0 was released on 2024-04-16.
> > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> > > IO-2.16.1 was released on 2024-04-08.
> > > COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> > > IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> > > PARENT-69 was released on 2024-04-01.
> > > IO-2.16.0 was released on 2024-03-28.
> > > LOGGING-1.3.1 was released on 2024-03-24.
> > > PARENT-68 was released on 2024-03-23.
> > > CONFIGURATION-2.10.1 was released on 2024-03-20.
> > > CONFIGURATION-2.10.0 was released on 2024-03-13.
> > >
> > > ## Community Health:
> > > We welcomed Claude Warren as our latest PMC member. Mailing list
> activity has
> > > increased. Most if not all of our increasing contributions are coming
> in
> > > through GitHub pull requests. This is working well for us:
> >
> > It is just one opinion, which I (still) do not share.
> > [Not denying the many utilities readily available from GH; the
> > issues lay elsewhere...]
> >
> > Gilles
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-

Re: [DRAFT] June Report to the Board

[Phil Steitz]

On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory 
wrote:

> On 2024/06/12 17:17:24 Phil Steitz wrote:
> > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> >
> > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory 
> wrote:
> > > >
> > > > Hello All,
> > > >
> > > > Here is the draft of our board report for June I plan on submitting
> in a
> > > day or so, feedback is welcome.
> > > >
> > > > ## Description:
> > > > The mission of Apache Commons is the creation and maintenance of Java
> > > focused
> > > > reusable libraries and components
> > > >
> > > > ## Project Status:
> > > > Current project status: Ongoing with moderate activity.
> > > > Issues for the board: none.
> > > >
> > > > ## Membership Data:
> > > > Apache Commons was founded 2007-06-19 (17 years ago)
> > > > There are currently 149 committers and 44 PMC members in this
> project.
> > > > The Committer-to-PMC ratio is roughly 5:2.
> > >
> > > Missing from this paragraph is the fact that Commons has enabled
> > > universal commit.
> > >
> > > > Community changes, past quarter:
> > > > - Claude Warren was added to the PMC on 2024-03-22
> > > > - No new committers. Last addition was Claude Warren on 2022-02-01.
> > > >
> > > > ## Project Activity:
> > > > Many releases of our components:
> > > > CONFIGUATION-2.11.0 was released on 2024-06-10.
> > >
> > > Is that a new component?
> > >
> > > > NET-3.11.1 was released on 2024-06-10.
> > > > PARENT-71 was released on 2024-06-10.
> > > > JEXL-3.4.0 was released on 2024-06-06.
> > > > NET-3.11.0 was released on 2024-05-31.
> > > > VALIDATOR-1.9.0 was released on 2024-05-28.
> > > > JCS-3.2.1 was released on 2024-05-27.
> > > > DAEMON-1.4.0 was released on 2024-05-24.
> > > > CLI-1.8.0 was released on 2024-05-23.
> > > > COMPRESS-1.26.2 was released on 2024-05-23.
> > > > LOGGING-1.3.2 was released on 2024-05-15.
> > > > PARENT-70 was released on 2024-05-15.
> > > > CSV-1.11.0 was released on 2024-05-02.
> > > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> > > > CLI-1.7.0 was released on 2024-04-18.
> > > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> > > > TEXT-1.12.0 was released on 2024-04-16.
> > > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> > > > IO-2.16.1 was released on 2024-04-08.
> > > > COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> > > > IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> > > > PARENT-69 was released on 2024-04-01.
> > > > IO-2.16.0 was released on 2024-03-28.
> > > > LOGGING-1.3.1 was released on 2024-03-24.
> > > > PARENT-68 was released on 2024-03-23.
> > > > CONFIGURATION-2.10.1 was released on 2024-03-20.
> > > > CONFIGURATION-2.10.0 was released on 2024-03-13.
> > >
> > > The above list should probably be sorted
> > >
> > > > ## Community Health:
> > > > We welcomed Claude Warren as our latest PMC member. Mailing list
> > > activity has
> > > > increased.
> > >
> > > Much of the increased mailing list activity is driven by dependabot
> > > PRs, many of which are useless, as it does not take Java compatibility
> > > into account.
> > >
> >
> > +1
> > I have had to filter out most of the messages and once I do that, there
> is
> > almost no actual discussion on-list.  I am worried that when people do
> try
> > to start discussion, the messages are being missed.  I personally see the
> > lack of ml discussion as a problem.  Lots of code changes are happening
> > with no discussion, other than maybe random nits on PRs ending up in
> github
> > threads that don't end up organized that well in list archives.  This
> > problem is not unique to Commons.
>
> Hi Phil,
>
> We had a discussion a while back about creating a "bot" email list but:
> - no one actually proposed anything concrete and did any work
> - we already have bot lists like "commit", "notifications", "issues",
> can't we reuse those?
>

+1 for that.  How about moving the dependabot things to "notifications"?
What exactly do we use that list for now?  I think it is important for
committers to monitor commits but that is not really possible with all of
the dependabot spam in there.  I personally filter that to /dev/null.

The problem with github PR comments basically replacing dev@ is a bigger
one.  It would be helpful if we could figure out a way to pipe (only) the
code discussion messages to the dev list, but I think the better answer
there would be to establish the discipline that any discussion beyond nits
gets moved to dev@.  That may be a dinosaur view, but I think it is worth
considering.  I agree with Gilles that fast processing of long-tail
one-shot PRs is useful but misleading when it comes to community health.
Steering people to dev@ and actually talking about the code might be
annoying to some in the long tail, but it might net us some new committers,
which IMO is more valuable than a lot of the one shot PRs that we get.

Phil


> - I don't know if GitHub lets us configure targe

Re: [VOTE] Release Apache Commons Collections 4.5.0-M2 based on RC1

[Phil Steitz]

+1

Build, sigs, notes, all look good to me.

Tested on
apache-maven-3.9.3
Java version: 17.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family:
"unix"

Some non-blocker comments:

0) There are quite a few javadoc warnings
1) SpotBugs errors should be suppressed or addressed
2) Checkstyle report is strangely wonky.  RAT is fine and headers look fine
to me, but Checkstyle is, um, confused

Phil

On Fri, Jun 14, 2024 at 7:49 PM Gary Gregory  wrote:

> We have fixed a few bugs and added enhancements since Apache Commons
> Collections 4.5.0-M1 was released, so I would like to release Apache
> Commons Collections 4.5.0-M2.
>
> Apache Commons Collections 4.5.0-M2 RC1 is available for review here:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1
> (svn revision 69753)
>
> The Git tag commons-collections-4.5.0-M2-RC1 commit for this RC is
> c92828a71367a4208d380e614f633d0196b5ad27 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=c92828a71367a4208d380e614f633d0196b5ad27
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-collections.git
> --branch
> 
> commons-collections-4.5.0-M2-RC1
> commons-collections-4.5.0-M2-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1743/org/apache/commons/commons-collections4/4.5.0-M2/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sat Jun 15 02:29:00 UTC 2024
>
> commons-collections4-4.5.0-M2-bin.tar.gz=277ec5079fe3d0e9783aaa49a9eb6e486b2f917f54ea369d6c3a0bfd38f4b0525f57ead9d2004615f459b0a3a1a0217d00f3638a2171afd504feb185992a6e38
>
> commons-collections4-4.5.0-M2-bin.zip=95fb06b1ab80d0769acc41ceef3349c2efe14513bf4ebb66b000b4781264c5054b04b275133b989f3080291deca3a8561b228910bb55588bbcdcaf47f938164c
>
> commons-collections4-4.5.0-M2-bom.json=a7cbaa38b9ba7e674f694ca0f71a45b9e787cf4ad42d7a2e220f36030dd7d3307c12f99f16dcbde7c8457cd76d554b5619d0fa88849f58096a86b71ee9077028
>
> commons-collections4-4.5.0-M2-bom.xml=11f612198e324da771eb6496a2fad59e884d368a0c008b5fa7943fceea1014a14dfdf7c7e49f23b87f67b6fc6fae01ed84fe4b842862461222e7f0b8d7e61aae
>
> commons-collections4-4.5.0-M2-javadoc.jar=8069b3bf23ddec37257147c73b03ed965f70afce721821294dea4c22b68b21963690409ad15f7e3eeb2b72b1151b5e4ca95f81c3c4a7a750716989269ab02890
>
> commons-collections4-4.5.0-M2-sources.jar=97a7ad53ea5539cc8730f3697f6114daa59f52f48ab913e1187ba5a595a7bdc7bd3a8d440efd9e6975d833b094debf3e62faf98818706fd9cad08b8fc34f4837
>
> commons-collections4-4.5.0-M2-src.tar.gz=8fe8c0c158254f44c7cc8744c9969e9a32fcd0642f56598c7a942da07c9fc88a6916cf07174e73f9a88f157fa0dbd56e829522f34b0c63ee129ebf923bcc42f7
>
> commons-collections4-4.5.0-M2-src.zip=32b8db011cd1c7a3b83b6ea2bb2b5c795636cf6ccaa83e277ecf1eb27f50469f3c5d3e1eedae606be190fad8baa1d5c04599701a6d84b52c0b56d44d7d1ec71d
>
> commons-collections4-4.5.0-M2-test-sources.jar=6dc1719b80f800be57dccfd05e959bc0f9f22aac0c9aca84c74b68d623e1bcae10346162347206fd28d66e4c8364d56c4e4998a4820898a259ca758c3054830d
>
> commons-collections4-4.5.0-M2-tests.jar=65b9e8f72a00daa586bba62e818aac348679f9afda5bcbf95c10d47e9d5e5e65c27518565ada2af56146ff09ccc1f5ad940eb123c3fb9c53bcc8624db3254e1c
>
> org.apache.commons_commons-collections4-4.5.0-M2.spdx.json=d3e8455335a09f92b7b1c470104384080d933d5f64d5fe96fde31645a1fef3168a5ce1f5f3be8a1f4da6318a11996a959c2485654b6ec9423d26c8347ff2294b
>
>
> I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
> -P jacoco -P japicmp clean package site deploy' using:
>
> openjdk version "17.0.11" 2024-04-16
> OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
>
> Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> Java version: 17.0.11, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
>
> Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
>
> Details of changes since 4.4 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/index.html
> (note some *relative* links are broken and the 4.5.0-M2
> directories are not yet created - these will be OK once the site is
> deployed.)
>
> JApiCmp Report (compared to 4.4):
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M

Re: [VOTE] Release Apache Commons Collections 4.5.0-M2 based on RC1

[Gary Gregory]

My +1

Gary

On Fri, Jun 14, 2024 at 10:48 PM Gary Gregory  wrote:
>
> We have fixed a few bugs and added enhancements since Apache Commons
> Collections 4.5.0-M1 was released, so I would like to release Apache
> Commons Collections 4.5.0-M2.
>
> Apache Commons Collections 4.5.0-M2 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1
> (svn revision 69753)
>
> The Git tag commons-collections-4.5.0-M2-RC1 commit for this RC is
> c92828a71367a4208d380e614f633d0196b5ad27 which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=c92828a71367a4208d380e614f633d0196b5ad27
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-collections.git
> --branch commons-collections-4.5.0-M2-RC1
> commons-collections-4.5.0-M2-RC1
>
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1743/org/apache/commons/commons-collections4/4.5.0-M2/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sat Jun 15 02:29:00 UTC 2024
> commons-collections4-4.5.0-M2-bin.tar.gz=277ec5079fe3d0e9783aaa49a9eb6e486b2f917f54ea369d6c3a0bfd38f4b0525f57ead9d2004615f459b0a3a1a0217d00f3638a2171afd504feb185992a6e38
> commons-collections4-4.5.0-M2-bin.zip=95fb06b1ab80d0769acc41ceef3349c2efe14513bf4ebb66b000b4781264c5054b04b275133b989f3080291deca3a8561b228910bb55588bbcdcaf47f938164c
> commons-collections4-4.5.0-M2-bom.json=a7cbaa38b9ba7e674f694ca0f71a45b9e787cf4ad42d7a2e220f36030dd7d3307c12f99f16dcbde7c8457cd76d554b5619d0fa88849f58096a86b71ee9077028
> commons-collections4-4.5.0-M2-bom.xml=11f612198e324da771eb6496a2fad59e884d368a0c008b5fa7943fceea1014a14dfdf7c7e49f23b87f67b6fc6fae01ed84fe4b842862461222e7f0b8d7e61aae
> commons-collections4-4.5.0-M2-javadoc.jar=8069b3bf23ddec37257147c73b03ed965f70afce721821294dea4c22b68b21963690409ad15f7e3eeb2b72b1151b5e4ca95f81c3c4a7a750716989269ab02890
> commons-collections4-4.5.0-M2-sources.jar=97a7ad53ea5539cc8730f3697f6114daa59f52f48ab913e1187ba5a595a7bdc7bd3a8d440efd9e6975d833b094debf3e62faf98818706fd9cad08b8fc34f4837
> commons-collections4-4.5.0-M2-src.tar.gz=8fe8c0c158254f44c7cc8744c9969e9a32fcd0642f56598c7a942da07c9fc88a6916cf07174e73f9a88f157fa0dbd56e829522f34b0c63ee129ebf923bcc42f7
> commons-collections4-4.5.0-M2-src.zip=32b8db011cd1c7a3b83b6ea2bb2b5c795636cf6ccaa83e277ecf1eb27f50469f3c5d3e1eedae606be190fad8baa1d5c04599701a6d84b52c0b56d44d7d1ec71d
> commons-collections4-4.5.0-M2-test-sources.jar=6dc1719b80f800be57dccfd05e959bc0f9f22aac0c9aca84c74b68d623e1bcae10346162347206fd28d66e4c8364d56c4e4998a4820898a259ca758c3054830d
> commons-collections4-4.5.0-M2-tests.jar=65b9e8f72a00daa586bba62e818aac348679f9afda5bcbf95c10d47e9d5e5e65c27518565ada2af56146ff09ccc1f5ad940eb123c3fb9c53bcc8624db3254e1c
> org.apache.commons_commons-collections4-4.5.0-M2.spdx.json=d3e8455335a09f92b7b1c470104384080d933d5f64d5fe96fde31645a1fef3168a5ce1f5f3be8a1f4da6318a11996a959c2485654b6ec9423d26c8347ff2294b
>
>
> I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
> -P jacoco -P japicmp clean package site deploy' using:
>
> openjdk version "17.0.11" 2024-04-16
> OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
>
> Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> Java version: 17.0.11, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
>
> Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
>
> Details of changes since 4.4 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/changes-report.html
>
> Site:
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/index.html
> (note some *relative* links are broken and the 4.5.0-M2
> directories are not yet created - these will be OK once the site is
> deployed.)
>
> JApiCmp Report (compared to 4.4):
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/japicmp.html
>
> RAT Report:
> 
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/rat-report.html
>
> KEYS:
>   https://downloads.apache.org/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,
>
> Gary Gregory,
> Release Manager (using key 86fdc7e2a11262cb)
>
> 

Re: [VOTE] Release Apache Commons Collections 4.5.0-M2 based on RC1

[Gary Gregory]

Thanks Phil, I'll look into these issues.

Gary

On Sat, Jun 15, 2024 at 1:01 PM Phil Steitz  wrote:
>
> +1
>
> Build, sigs, notes, all look good to me.
>
> Tested on
> apache-maven-3.9.3
> Java version: 17.0.11, vendor: Ubuntu, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family:
> "unix"
>
> Some non-blocker comments:
>
> 0) There are quite a few javadoc warnings
> 1) SpotBugs errors should be suppressed or addressed
> 2) Checkstyle report is strangely wonky.  RAT is fine and headers look fine
> to me, but Checkstyle is, um, confused
>
> Phil
>
> On Fri, Jun 14, 2024 at 7:49 PM Gary Gregory  wrote:
>
> > We have fixed a few bugs and added enhancements since Apache Commons
> > Collections 4.5.0-M1 was released, so I would like to release Apache
> > Commons Collections 4.5.0-M2.
> >
> > Apache Commons Collections 4.5.0-M2 RC1 is available for review here:
> >
> > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1
> > (svn revision 69753)
> >
> > The Git tag commons-collections-4.5.0-M2-RC1 commit for this RC is
> > c92828a71367a4208d380e614f633d0196b5ad27 which you can browse here:
> >
> > https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=c92828a71367a4208d380e614f633d0196b5ad27
> > You may checkout this tag using:
> > git clone https://gitbox.apache.org/repos/asf/commons-collections.git
> > --branch
> > 
> > commons-collections-4.5.0-M2-RC1
> > commons-collections-4.5.0-M2-RC1
> >
> > Maven artifacts are here:
> >
> > https://repository.apache.org/content/repositories/orgapachecommons-1743/org/apache/commons/commons-collections4/4.5.0-M2/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > #Sat Jun 15 02:29:00 UTC 2024
> >
> > commons-collections4-4.5.0-M2-bin.tar.gz=277ec5079fe3d0e9783aaa49a9eb6e486b2f917f54ea369d6c3a0bfd38f4b0525f57ead9d2004615f459b0a3a1a0217d00f3638a2171afd504feb185992a6e38
> >
> > commons-collections4-4.5.0-M2-bin.zip=95fb06b1ab80d0769acc41ceef3349c2efe14513bf4ebb66b000b4781264c5054b04b275133b989f3080291deca3a8561b228910bb55588bbcdcaf47f938164c
> >
> > commons-collections4-4.5.0-M2-bom.json=a7cbaa38b9ba7e674f694ca0f71a45b9e787cf4ad42d7a2e220f36030dd7d3307c12f99f16dcbde7c8457cd76d554b5619d0fa88849f58096a86b71ee9077028
> >
> > commons-collections4-4.5.0-M2-bom.xml=11f612198e324da771eb6496a2fad59e884d368a0c008b5fa7943fceea1014a14dfdf7c7e49f23b87f67b6fc6fae01ed84fe4b842862461222e7f0b8d7e61aae
> >
> > commons-collections4-4.5.0-M2-javadoc.jar=8069b3bf23ddec37257147c73b03ed965f70afce721821294dea4c22b68b21963690409ad15f7e3eeb2b72b1151b5e4ca95f81c3c4a7a750716989269ab02890
> >
> > commons-collections4-4.5.0-M2-sources.jar=97a7ad53ea5539cc8730f3697f6114daa59f52f48ab913e1187ba5a595a7bdc7bd3a8d440efd9e6975d833b094debf3e62faf98818706fd9cad08b8fc34f4837
> >
> > commons-collections4-4.5.0-M2-src.tar.gz=8fe8c0c158254f44c7cc8744c9969e9a32fcd0642f56598c7a942da07c9fc88a6916cf07174e73f9a88f157fa0dbd56e829522f34b0c63ee129ebf923bcc42f7
> >
> > commons-collections4-4.5.0-M2-src.zip=32b8db011cd1c7a3b83b6ea2bb2b5c795636cf6ccaa83e277ecf1eb27f50469f3c5d3e1eedae606be190fad8baa1d5c04599701a6d84b52c0b56d44d7d1ec71d
> >
> > commons-collections4-4.5.0-M2-test-sources.jar=6dc1719b80f800be57dccfd05e959bc0f9f22aac0c9aca84c74b68d623e1bcae10346162347206fd28d66e4c8364d56c4e4998a4820898a259ca758c3054830d
> >
> > commons-collections4-4.5.0-M2-tests.jar=65b9e8f72a00daa586bba62e818aac348679f9afda5bcbf95c10d47e9d5e5e65c27518565ada2af56146ff09ccc1f5ad940eb123c3fb9c53bcc8624db3254e1c
> >
> > org.apache.commons_commons-collections4-4.5.0-M2.spdx.json=d3e8455335a09f92b7b1c470104384080d933d5f64d5fe96fde31645a1fef3168a5ce1f5f3be8a1f4da6318a11996a959c2485654b6ec9423d26c8347ff2294b
> >
> >
> > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
> > -P jacoco -P japicmp clean package site deploy' using:
> >
> > openjdk version "17.0.11" 2024-04-16
> > OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> >
> > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> > Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> > Java version: 17.0.11, vendor: Homebrew, runtime:
> > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> >
> > Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> >
> > Details of changes since 4.4 are in the release notes:
> >
> > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/RELEASE-NOTES.txt
> >
> > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M2-RC1/site/changes-report.html
> >
> > Site:
> >
> > https://dist.apache.org/repos/dist/dev/common

Re: [COLLECTIONS] documentation question

[Gary Gregory]

We (well, not me) are revamping the Log4j site documentation using
AsciiDoc. Take a look there if you're curious.

Gary

On Sat, Jun 15, 2024 at 12:07 PM Phil Steitz  wrote:
>
> On Sat, Jun 15, 2024 at 8:19 AM Claude Warren  wrote:
>
> > Greetings,
> >
> > I see that we support xml documents for documentation but does anyone know
> > if markdown is supported?  I have a number of markdown based documents that
> > would work well for the Bloom filter documentation, but translating to XML
> > will be a pain.
> >
>
> I know in the past some sites have used the now archaic apt format along
> with the similarly ancient xdoc that most sites use.  I think the maven
> site plugin allows you to combine content from different formats and
> markdown is now a supported format, so this should not be a problem.  I
> don't think you need to transform all of the site content to do that, but I
> doubt anyone would complain - and many would be thankful - if you did.  See
> [1].
>
> Phil
> [1]
> https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
>
>
> >
> > thanks,
> > Claude
> >

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

Re: [COLLECTIONS] documentation question

[Gary Gregory]

Feel free to write the docs in whatever format you want :-) It just
needs to build with Maven (prefereably)

Gary

On Sat, Jun 15, 2024 at 12:07 PM Phil Steitz  wrote:
>
> On Sat, Jun 15, 2024 at 8:19 AM Claude Warren  wrote:
>
> > Greetings,
> >
> > I see that we support xml documents for documentation but does anyone know
> > if markdown is supported?  I have a number of markdown based documents that
> > would work well for the Bloom filter documentation, but translating to XML
> > will be a pain.
> >
>
> I know in the past some sites have used the now archaic apt format along
> with the similarly ancient xdoc that most sites use.  I think the maven
> site plugin allows you to combine content from different formats and
> markdown is now a supported format, so this should not be a problem.  I
> don't think you need to transform all of the site content to do that, but I
> doubt anyone would complain - and many would be thankful - if you did.  See
> [1].
>
> Phil
> [1]
> https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
>
>
> >
> > thanks,
> > Claude
> >

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

Re: [DRAFT] June Report to the Board

[Gary Gregory]

Note that it is 1) awkward to say "Let's stop talking about this PR in
this PR" and 2) "You need to subscribe to a mailing to continue this
chat." It's just hard to find when to ask for a switch. Especially
when GH has a nice UI to make comments _about code_. Over at Log4j, we
now use GitHub issues instead of Jira, furthering the split...

Gary

On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz  wrote:
>
> On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory 
> wrote:
>
> > On 2024/06/12 17:17:24 Phil Steitz wrote:
> > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> > >
> > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory 
> > wrote:
> > > > >
> > > > > Hello All,
> > > > >
> > > > > Here is the draft of our board report for June I plan on submitting
> > in a
> > > > day or so, feedback is welcome.
> > > > >
> > > > > ## Description:
> > > > > The mission of Apache Commons is the creation and maintenance of Java
> > > > focused
> > > > > reusable libraries and components
> > > > >
> > > > > ## Project Status:
> > > > > Current project status: Ongoing with moderate activity.
> > > > > Issues for the board: none.
> > > > >
> > > > > ## Membership Data:
> > > > > Apache Commons was founded 2007-06-19 (17 years ago)
> > > > > There are currently 149 committers and 44 PMC members in this
> > project.
> > > > > The Committer-to-PMC ratio is roughly 5:2.
> > > >
> > > > Missing from this paragraph is the fact that Commons has enabled
> > > > universal commit.
> > > >
> > > > > Community changes, past quarter:
> > > > > - Claude Warren was added to the PMC on 2024-03-22
> > > > > - No new committers. Last addition was Claude Warren on 2022-02-01.
> > > > >
> > > > > ## Project Activity:
> > > > > Many releases of our components:
> > > > > CONFIGUATION-2.11.0 was released on 2024-06-10.
> > > >
> > > > Is that a new component?
> > > >
> > > > > NET-3.11.1 was released on 2024-06-10.
> > > > > PARENT-71 was released on 2024-06-10.
> > > > > JEXL-3.4.0 was released on 2024-06-06.
> > > > > NET-3.11.0 was released on 2024-05-31.
> > > > > VALIDATOR-1.9.0 was released on 2024-05-28.
> > > > > JCS-3.2.1 was released on 2024-05-27.
> > > > > DAEMON-1.4.0 was released on 2024-05-24.
> > > > > CLI-1.8.0 was released on 2024-05-23.
> > > > > COMPRESS-1.26.2 was released on 2024-05-23.
> > > > > LOGGING-1.3.2 was released on 2024-05-15.
> > > > > PARENT-70 was released on 2024-05-15.
> > > > > CSV-1.11.0 was released on 2024-05-02.
> > > > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> > > > > CLI-1.7.0 was released on 2024-04-18.
> > > > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> > > > > TEXT-1.12.0 was released on 2024-04-16.
> > > > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> > > > > IO-2.16.1 was released on 2024-04-08.
> > > > > COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> > > > > IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> > > > > PARENT-69 was released on 2024-04-01.
> > > > > IO-2.16.0 was released on 2024-03-28.
> > > > > LOGGING-1.3.1 was released on 2024-03-24.
> > > > > PARENT-68 was released on 2024-03-23.
> > > > > CONFIGURATION-2.10.1 was released on 2024-03-20.
> > > > > CONFIGURATION-2.10.0 was released on 2024-03-13.
> > > >
> > > > The above list should probably be sorted
> > > >
> > > > > ## Community Health:
> > > > > We welcomed Claude Warren as our latest PMC member. Mailing list
> > > > activity has
> > > > > increased.
> > > >
> > > > Much of the increased mailing list activity is driven by dependabot
> > > > PRs, many of which are useless, as it does not take Java compatibility
> > > > into account.
> > > >
> > >
> > > +1
> > > I have had to filter out most of the messages and once I do that, there
> > is
> > > almost no actual discussion on-list.  I am worried that when people do
> > try
> > > to start discussion, the messages are being missed.  I personally see the
> > > lack of ml discussion as a problem.  Lots of code changes are happening
> > > with no discussion, other than maybe random nits on PRs ending up in
> > github
> > > threads that don't end up organized that well in list archives.  This
> > > problem is not unique to Commons.
> >
> > Hi Phil,
> >
> > We had a discussion a while back about creating a "bot" email list but:
> > - no one actually proposed anything concrete and did any work
> > - we already have bot lists like "commit", "notifications", "issues",
> > can't we reuse those?
> >
>
> +1 for that.  How about moving the dependabot things to "notifications"?
> What exactly do we use that list for now?  I think it is important for
> committers to monitor commits but that is not really possible with all of
> the dependabot spam in there.  I personally filter that to /dev/null.
>
> The problem with github PR comments basically replacing dev@ is a bigger
> one.  It would be helpful if we could figure out a way to pipe (only) the
> code discussion 

[VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

[Gary Gregory]

We have fixed a few bugs and added enhancements since Apache Commons
Email Parent POM 1.6.0 was released, so I would like to release Apache
Commons Email Parent POM 2.0.0-M1.

The reason for a major new release is to deal with the horror show of
Javax vs.Jakarta namespaces.

Apache Commons Email Parent POM 2.0.0-M1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1
(svn revision 69780)

The Git tag commons-email-2.0.0-M1-RC1 commit for this RC is
a514720114343be667e886123eddc90b36e72038 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=a514720114343be667e886123eddc90b36e72038
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-email.git
--branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1749/org/apache/commons/commons-email2-parent/2.0.0-M1/

These are the artifacts and their hashes:

#Release SHA-512s
source/commons-email2-2.0.0-M1-src.tar.gz=9f2250cd484079e0d08cac0982985aae5261b87c42a36a4eaf61d6948e5afe0e43310819d6f442a864d95643b613dc2f197e455ab485afe794d614391145737d
source/commons-email2-2.0.0-M1-src.zip=d9c8f206e0fd3e5b1fb38ea67d2e8f15eec53e340a64d4db0b253bfdf7edbad70710eb1ae6b0227b8926c072dc12e9772f1dbc9539217df8bb458318f700ab15
binaries/commons-email2-2.0.0-M1-bin.tar.gz=c3ee2d6e0346f8bb15b9890767cd990353814cfacf18b8437f66fa573d63031f8ff47ce1d8de2868d5fa2ab4d04694e3aa1d8bd73faec5f3dea461c109ac8320
binaries/commons-email2-2.0.0-M1-bin.zip=ba1207159f5c833bde93c691185da4114c040978b4454cab164582a3b633d86a49ebd91167c1786d7337d9faae982823ad5d4c24467abda9ca3331c3d24c1027

I have tested this with 'mvn' (default goal) using:

openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)

Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
Maven home: /usr/local/Cellar/maven/3.9.7/libexec
Java version: 17.0.11, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"

Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64

Details of changes since 1.6.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/index.html
(note some *relative* links are broken and the 2.0.0-M1
directories are not yet created - these will be OK once the site is
deployed.)
There is no JApiCmp report in this major release.,

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/rat-report.html

KEYS:
  https://downloads.apache.org/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,

Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)

For 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.

1a) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-email.git
--branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
cd commons-email-2.0.0-M1-RC1

1b) Download and unpack the source archive from:

https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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) Check binary compatibility

Older components still use Apache Clirr:

This step is not required if the site includes a Clirr report page
which you then must check.

mvn clirr:check

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page
which you then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) 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

5) Build the site for a single module project

Note: Some plugins require the components to be installed instead of packaged.

mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

6) Build 

Re: [DRAFT] June Report to the Board

[Phil Steitz]

On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory 
wrote:

> Note that it is 1) awkward to say "Let's stop talking about this PR in
> this PR"


Funny we used to do that all the time in Jira comments.  I guess times
change.  FWIW, I think it is a step backward in discussion and ultimately
code and archive quality.  To me it is "awkward" to have to be constantly
@somebody and not have threads or definitive discussion anywhere.  Works
fine for trivial changes but does not really work for substantive
discussion of bigger things.  So we end up never actually having those
discussions and there is no reasonably searchable archive of the thought
process that led to the changes going in.  We used to have that and it was
a useful thing, especially for the more complex components.

Phil



> and 2) "You need to subscribe to a mailing to continue this
> chat." It's just hard to find when to ask for a switch. Especially
> when GH has a nice UI to make comments _about code_. Over at Log4j, we
> now use GitHub issues instead of Jira, furthering the split...
>
> Gary
>
> On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz 
> wrote:
> >
> > On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory 
> > wrote:
> >
> > > On 2024/06/12 17:17:24 Phil Steitz wrote:
> > > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> > > >
> > > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory  >
> > > wrote:
> > > > > >
> > > > > > Hello All,
> > > > > >
> > > > > > Here is the draft of our board report for June I plan on
> submitting
> > > in a
> > > > > day or so, feedback is welcome.
> > > > > >
> > > > > > ## Description:
> > > > > > The mission of Apache Commons is the creation and maintenance of
> Java
> > > > > focused
> > > > > > reusable libraries and components
> > > > > >
> > > > > > ## Project Status:
> > > > > > Current project status: Ongoing with moderate activity.
> > > > > > Issues for the board: none.
> > > > > >
> > > > > > ## Membership Data:
> > > > > > Apache Commons was founded 2007-06-19 (17 years ago)
> > > > > > There are currently 149 committers and 44 PMC members in this
> > > project.
> > > > > > The Committer-to-PMC ratio is roughly 5:2.
> > > > >
> > > > > Missing from this paragraph is the fact that Commons has enabled
> > > > > universal commit.
> > > > >
> > > > > > Community changes, past quarter:
> > > > > > - Claude Warren was added to the PMC on 2024-03-22
> > > > > > - No new committers. Last addition was Claude Warren on
> 2022-02-01.
> > > > > >
> > > > > > ## Project Activity:
> > > > > > Many releases of our components:
> > > > > > CONFIGUATION-2.11.0 was released on 2024-06-10.
> > > > >
> > > > > Is that a new component?
> > > > >
> > > > > > NET-3.11.1 was released on 2024-06-10.
> > > > > > PARENT-71 was released on 2024-06-10.
> > > > > > JEXL-3.4.0 was released on 2024-06-06.
> > > > > > NET-3.11.0 was released on 2024-05-31.
> > > > > > VALIDATOR-1.9.0 was released on 2024-05-28.
> > > > > > JCS-3.2.1 was released on 2024-05-27.
> > > > > > DAEMON-1.4.0 was released on 2024-05-24.
> > > > > > CLI-1.8.0 was released on 2024-05-23.
> > > > > > COMPRESS-1.26.2 was released on 2024-05-23.
> > > > > > LOGGING-1.3.2 was released on 2024-05-15.
> > > > > > PARENT-70 was released on 2024-05-15.
> > > > > > CSV-1.11.0 was released on 2024-05-02.
> > > > > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> > > > > > CLI-1.7.0 was released on 2024-04-18.
> > > > > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> > > > > > TEXT-1.12.0 was released on 2024-04-16.
> > > > > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> > > > > > IO-2.16.1 was released on 2024-04-08.
> > > > > > COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> > > > > > IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> > > > > > PARENT-69 was released on 2024-04-01.
> > > > > > IO-2.16.0 was released on 2024-03-28.
> > > > > > LOGGING-1.3.1 was released on 2024-03-24.
> > > > > > PARENT-68 was released on 2024-03-23.
> > > > > > CONFIGURATION-2.10.1 was released on 2024-03-20.
> > > > > > CONFIGURATION-2.10.0 was released on 2024-03-13.
> > > > >
> > > > > The above list should probably be sorted
> > > > >
> > > > > > ## Community Health:
> > > > > > We welcomed Claude Warren as our latest PMC member. Mailing list
> > > > > activity has
> > > > > > increased.
> > > > >
> > > > > Much of the increased mailing list activity is driven by dependabot
> > > > > PRs, many of which are useless, as it does not take Java
> compatibility
> > > > > into account.
> > > > >
> > > >
> > > > +1
> > > > I have had to filter out most of the messages and once I do that,
> there
> > > is
> > > > almost no actual discussion on-list.  I am worried that when people
> do
> > > try
> > > > to start discussion, the messages are being missed.  I personally
> see the
> > > > lack of ml discussion as a problem.  Lots of code changes are
> happening
> > > > with no d

Re: [DRAFT] June Report to the Board

[Gary Gregory]

If we want to have everything recorded in one place, then we need to put up
some roadblocks to PRs, the Wiki, and Jira like ... what? Have a PR, wiki,
and Jira template/gate that says... you must discuss your issue/bug/feature
first on the mailing list? It does not feel workable.

I don't think this is about people being dinosaurs, it's just the
technology and processes that are changing. I really like working with
GitHub PRs and GitHub CI builds. I don't want to go back to emails only
just like don't ever want to use an IRC thing.

Some people don't want to create a GitHub account, so it's Jira and diff
files for them, but that's rare. BUT it gives us a LOT MORE work to
validate a patch compared to GitHub CI where it can use many OSs and Java
version while I'm sleeping :-)

Gary


On Sat, Jun 15, 2024, 2:00 PM Phil Steitz  wrote:

> On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory 
> wrote:
>
> > Note that it is 1) awkward to say "Let's stop talking about this PR in
> > this PR"
>
>
> Funny we used to do that all the time in Jira comments.  I guess times
> change.  FWIW, I think it is a step backward in discussion and ultimately
> code and archive quality.  To me it is "awkward" to have to be constantly
> @somebody and not have threads or definitive discussion anywhere.  Works
> fine for trivial changes but does not really work for substantive
> discussion of bigger things.  So we end up never actually having those
> discussions and there is no reasonably searchable archive of the thought
> process that led to the changes going in.  We used to have that and it was
> a useful thing, especially for the more complex components.
>
> Phil
>
>
>
> > and 2) "You need to subscribe to a mailing to continue this
> > chat." It's just hard to find when to ask for a switch. Especially
> > when GH has a nice UI to make comments _about code_. Over at Log4j, we
> > now use GitHub issues instead of Jira, furthering the split...
> >
> > Gary
> >
> > On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz 
> > wrote:
> > >
> > > On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory 
> > > wrote:
> > >
> > > > On 2024/06/12 17:17:24 Phil Steitz wrote:
> > > > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> > > > >
> > > > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory <
> ggreg...@apache.org
> > >
> > > > wrote:
> > > > > > >
> > > > > > > Hello All,
> > > > > > >
> > > > > > > Here is the draft of our board report for June I plan on
> > submitting
> > > > in a
> > > > > > day or so, feedback is welcome.
> > > > > > >
> > > > > > > ## Description:
> > > > > > > The mission of Apache Commons is the creation and maintenance
> of
> > Java
> > > > > > focused
> > > > > > > reusable libraries and components
> > > > > > >
> > > > > > > ## Project Status:
> > > > > > > Current project status: Ongoing with moderate activity.
> > > > > > > Issues for the board: none.
> > > > > > >
> > > > > > > ## Membership Data:
> > > > > > > Apache Commons was founded 2007-06-19 (17 years ago)
> > > > > > > There are currently 149 committers and 44 PMC members in this
> > > > project.
> > > > > > > The Committer-to-PMC ratio is roughly 5:2.
> > > > > >
> > > > > > Missing from this paragraph is the fact that Commons has enabled
> > > > > > universal commit.
> > > > > >
> > > > > > > Community changes, past quarter:
> > > > > > > - Claude Warren was added to the PMC on 2024-03-22
> > > > > > > - No new committers. Last addition was Claude Warren on
> > 2022-02-01.
> > > > > > >
> > > > > > > ## Project Activity:
> > > > > > > Many releases of our components:
> > > > > > > CONFIGUATION-2.11.0 was released on 2024-06-10.
> > > > > >
> > > > > > Is that a new component?
> > > > > >
> > > > > > > NET-3.11.1 was released on 2024-06-10.
> > > > > > > PARENT-71 was released on 2024-06-10.
> > > > > > > JEXL-3.4.0 was released on 2024-06-06.
> > > > > > > NET-3.11.0 was released on 2024-05-31.
> > > > > > > VALIDATOR-1.9.0 was released on 2024-05-28.
> > > > > > > JCS-3.2.1 was released on 2024-05-27.
> > > > > > > DAEMON-1.4.0 was released on 2024-05-24.
> > > > > > > CLI-1.8.0 was released on 2024-05-23.
> > > > > > > COMPRESS-1.26.2 was released on 2024-05-23.
> > > > > > > LOGGING-1.3.2 was released on 2024-05-15.
> > > > > > > PARENT-70 was released on 2024-05-15.
> > > > > > > CSV-1.11.0 was released on 2024-05-02.
> > > > > > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
> > > > > > > CLI-1.7.0 was released on 2024-04-18.
> > > > > > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
> > > > > > > TEXT-1.12.0 was released on 2024-04-16.
> > > > > > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
> > > > > > > IO-2.16.1 was released on 2024-04-08.
> > > > > > > COLLECTIONS-4.5.0-M1 was released on 2024-04-02.
> > > > > > > IMAGING-1.0.0-alpha4 was released on 2024-04-02.
> > > > > > > PARENT-69 was released on 2024-04-01.
> > > > > > > IO-2.16.0 was released on 2024-0

Re: [DRAFT] June Report to the Board

[Gary Gregory]

Hm, would using GitHub Issues instead of Jira make the trail following
easier, harder, or the same?

Gary

On Sat, Jun 15, 2024, 2:58 PM Gary Gregory  wrote:

> If we want to have everything recorded in one place, then we need to put
> up some roadblocks to PRs, the Wiki, and Jira like ... what? Have a PR,
> wiki, and Jira template/gate that says... you must discuss your
> issue/bug/feature first on the mailing list? It does not feel workable.
>
> I don't think this is about people being dinosaurs, it's just the
> technology and processes that are changing. I really like working with
> GitHub PRs and GitHub CI builds. I don't want to go back to emails only
> just like don't ever want to use an IRC thing.
>
> Some people don't want to create a GitHub account, so it's Jira and diff
> files for them, but that's rare. BUT it gives us a LOT MORE work to
> validate a patch compared to GitHub CI where it can use many OSs and Java
> version while I'm sleeping :-)
>
> Gary
>
>
> On Sat, Jun 15, 2024, 2:00 PM Phil Steitz  wrote:
>
>> On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory 
>> wrote:
>>
>> > Note that it is 1) awkward to say "Let's stop talking about this PR in
>> > this PR"
>>
>>
>> Funny we used to do that all the time in Jira comments.  I guess times
>> change.  FWIW, I think it is a step backward in discussion and ultimately
>> code and archive quality.  To me it is "awkward" to have to be constantly
>> @somebody and not have threads or definitive discussion anywhere.  Works
>> fine for trivial changes but does not really work for substantive
>> discussion of bigger things.  So we end up never actually having those
>> discussions and there is no reasonably searchable archive of the thought
>> process that led to the changes going in.  We used to have that and it was
>> a useful thing, especially for the more complex components.
>>
>> Phil
>>
>>
>>
>> > and 2) "You need to subscribe to a mailing to continue this
>> > chat." It's just hard to find when to ask for a switch. Especially
>> > when GH has a nice UI to make comments _about code_. Over at Log4j, we
>> > now use GitHub issues instead of Jira, furthering the split...
>> >
>> > Gary
>> >
>> > On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz 
>> > wrote:
>> > >
>> > > On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory > >
>> > > wrote:
>> > >
>> > > > On 2024/06/12 17:17:24 Phil Steitz wrote:
>> > > > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
>> > > > >
>> > > > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory <
>> ggreg...@apache.org
>> > >
>> > > > wrote:
>> > > > > > >
>> > > > > > > Hello All,
>> > > > > > >
>> > > > > > > Here is the draft of our board report for June I plan on
>> > submitting
>> > > > in a
>> > > > > > day or so, feedback is welcome.
>> > > > > > >
>> > > > > > > ## Description:
>> > > > > > > The mission of Apache Commons is the creation and maintenance
>> of
>> > Java
>> > > > > > focused
>> > > > > > > reusable libraries and components
>> > > > > > >
>> > > > > > > ## Project Status:
>> > > > > > > Current project status: Ongoing with moderate activity.
>> > > > > > > Issues for the board: none.
>> > > > > > >
>> > > > > > > ## Membership Data:
>> > > > > > > Apache Commons was founded 2007-06-19 (17 years ago)
>> > > > > > > There are currently 149 committers and 44 PMC members in this
>> > > > project.
>> > > > > > > The Committer-to-PMC ratio is roughly 5:2.
>> > > > > >
>> > > > > > Missing from this paragraph is the fact that Commons has enabled
>> > > > > > universal commit.
>> > > > > >
>> > > > > > > Community changes, past quarter:
>> > > > > > > - Claude Warren was added to the PMC on 2024-03-22
>> > > > > > > - No new committers. Last addition was Claude Warren on
>> > 2022-02-01.
>> > > > > > >
>> > > > > > > ## Project Activity:
>> > > > > > > Many releases of our components:
>> > > > > > > CONFIGUATION-2.11.0 was released on 2024-06-10.
>> > > > > >
>> > > > > > Is that a new component?
>> > > > > >
>> > > > > > > NET-3.11.1 was released on 2024-06-10.
>> > > > > > > PARENT-71 was released on 2024-06-10.
>> > > > > > > JEXL-3.4.0 was released on 2024-06-06.
>> > > > > > > NET-3.11.0 was released on 2024-05-31.
>> > > > > > > VALIDATOR-1.9.0 was released on 2024-05-28.
>> > > > > > > JCS-3.2.1 was released on 2024-05-27.
>> > > > > > > DAEMON-1.4.0 was released on 2024-05-24.
>> > > > > > > CLI-1.8.0 was released on 2024-05-23.
>> > > > > > > COMPRESS-1.26.2 was released on 2024-05-23.
>> > > > > > > LOGGING-1.3.2 was released on 2024-05-15.
>> > > > > > > PARENT-70 was released on 2024-05-15.
>> > > > > > > CSV-1.11.0 was released on 2024-05-02.
>> > > > > > > RELEASE-PLUGIN-1.8.2 was released on 2024-04-19.
>> > > > > > > CLI-1.7.0 was released on 2024-04-18.
>> > > > > > > IMAGING-1.0.0-alpha5 was released on 2024-04-18.
>> > > > > > > TEXT-1.12.0 was released on 2024-04-16.
>> > > > > > > BUILD-PLUGIN-1.14.0 was released on 2024-04-15.
>> 

Re: [apache/commons-lang] Reimplement RandomStringUtils on top of SecureRandom#getInstanceStrong() (PR #1235)

[Phil Steitz]

On Fri, Jun 14, 2024 at 4:13 PM Fabrice Benhamouda 
wrote:

> Thanks @psteitz  ! I am not sure where is the
> best place to post the following comment. If you think it’s more
> appropriate to post it to the mailing list, let me know and I will post it
> there.
>
> To address the point "1) gen time performance cost", I’ve written some
> optimizations on top of the current PR: garydgregory#2
> 
>
> Benchmarking using JMH with JDK 8 on an AWS c6a.xlarge instance with
> cryptographic providers SUN/NativePRNG, SUN/SHA1PRNG, ACCP
>  1.6, and
> ACCP  2.3,
> we have the following results. Compared to the current state (with the
> default java.util.Random/ThreadLocalRandom number generator), when any of
> the above SecureRandom is used with the optimized code, the time to
> generate random alphabetic, alphanumeric, and numeric strings of at least
> 16 characters is less than three times slower (and sometimes even 5x
> faster). For 4-character strings, we observe a slow-down of at most 8x.
>
> If the optimized RandomStringUtils is called concurrently in multiple
> threads, the SUN/NativePrng SecureRandom implementation (the default on
> Linux) may be slower as calls are serialized (due to access to/dev/random.
>
This is the use case I would be most concerned with.  Many web applications
use this class in multi-threaded app server settings.  I would not use the
class in web apps after this change for that reason.  If we do make the
change, we should make it clear in the class javadoc that it is using
SecureRandom and prone to occasional stalls.

Since there was no discussion about why this change is being made, I will
ask again why it is being proposed.  The only rationale that I can see is
that somehow some users are using the class to generate things that should
be cryptographically secure, like passwords or hash salt, so to protect
these users, we make all other users take a potential performance hit.
Much better, IMO, would be to make the recommended improvements in
performance to the vanilla Random-based impl and add a new class or somehow
shoehorn in a secure impl for users that want / need that.

Phil

This seems an unlikely scenario in practice. In addition, switching to ACCP
2 for SecureRandom would fix the performance issue in that case.

> —
> Reply to this email directly, view it on GitHub
> ,
> or unsubscribe
> 
> .
> You are receiving this because you were mentioned.Message ID:
> 
>

Re: [DRAFT] June Report to the Board

[Phil Steitz]

On Sat, Jun 15, 2024 at 12:27 PM Gary Gregory 
wrote:

> Hm, would using GitHub Issues instead of Jira make the trail following
> easier, harder, or the same?
>

Harder, because then you would have to search yet another place to
reconstruct history.  But that would be less of an issue over time.  I
don't see how it would make it better.  What bugs me is not so much having
to look in multiple places as the degraded discussion.  We never had
"roadblocks" before - just a convention that we use the dev list to talk
about substantive issues.  JIRA (or Bugzilla or Github Issues or
) is for users to report bugs, ask for enhancements,
organize work, mark things as done. etc.  commits@, github PR review,
next_cool_review_board  is to enable review of proposed or committed code.
The ML is for discussion.  Trying to force all discussion into PR "threads"
has two big problems: 0) it lacks threading and unless we just drop dev@ it
fragments discussion 1) it causes things to be discussed late.  It works
great for trivial changes but for things that significantly change
performance or behavior or where there are a lot of different ways they
could be done, it is way better to actually talk about them rather than
just hack a PR and try to collectively mutate it into something acceptable.

Phil

>
> Gary
>
> On Sat, Jun 15, 2024, 2:58 PM Gary Gregory 
> wrote:
>
> > If we want to have everything recorded in one place, then we need to put
> > up some roadblocks to PRs, the Wiki, and Jira like ... what? Have a PR,
> > wiki, and Jira template/gate that says... you must discuss your
> > issue/bug/feature first on the mailing list? It does not feel workable.
> >
> > I don't think this is about people being dinosaurs, it's just the
> > technology and processes that are changing. I really like working with
> > GitHub PRs and GitHub CI builds. I don't want to go back to emails only
> > just like don't ever want to use an IRC thing.
> >
> > Some people don't want to create a GitHub account, so it's Jira and diff
> > files for them, but that's rare. BUT it gives us a LOT MORE work to
> > validate a patch compared to GitHub CI where it can use many OSs and Java
> > version while I'm sleeping :-)
> >
> > Gary
> >
> >
> > On Sat, Jun 15, 2024, 2:00 PM Phil Steitz  wrote:
> >
> >> On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory 
> >> wrote:
> >>
> >> > Note that it is 1) awkward to say "Let's stop talking about this PR in
> >> > this PR"
> >>
> >>
> >> Funny we used to do that all the time in Jira comments.  I guess times
> >> change.  FWIW, I think it is a step backward in discussion and
> ultimately
> >> code and archive quality.  To me it is "awkward" to have to be
> constantly
> >> @somebody and not have threads or definitive discussion anywhere.  Works
> >> fine for trivial changes but does not really work for substantive
> >> discussion of bigger things.  So we end up never actually having those
> >> discussions and there is no reasonably searchable archive of the thought
> >> process that led to the changes going in.  We used to have that and it
> was
> >> a useful thing, especially for the more complex components.
> >>
> >> Phil
> >>
> >>
> >>
> >> > and 2) "You need to subscribe to a mailing to continue this
> >> > chat." It's just hard to find when to ask for a switch. Especially
> >> > when GH has a nice UI to make comments _about code_. Over at Log4j, we
> >> > now use GitHub issues instead of Jira, furthering the split...
> >> >
> >> > Gary
> >> >
> >> > On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz 
> >> > wrote:
> >> > >
> >> > > On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory <
> ggreg...@apache.org
> >> >
> >> > > wrote:
> >> > >
> >> > > > On 2024/06/12 17:17:24 Phil Steitz wrote:
> >> > > > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> >> > > > >
> >> > > > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory <
> >> ggreg...@apache.org
> >> > >
> >> > > > wrote:
> >> > > > > > >
> >> > > > > > > Hello All,
> >> > > > > > >
> >> > > > > > > Here is the draft of our board report for June I plan on
> >> > submitting
> >> > > > in a
> >> > > > > > day or so, feedback is welcome.
> >> > > > > > >
> >> > > > > > > ## Description:
> >> > > > > > > The mission of Apache Commons is the creation and
> maintenance
> >> of
> >> > Java
> >> > > > > > focused
> >> > > > > > > reusable libraries and components
> >> > > > > > >
> >> > > > > > > ## Project Status:
> >> > > > > > > Current project status: Ongoing with moderate activity.
> >> > > > > > > Issues for the board: none.
> >> > > > > > >
> >> > > > > > > ## Membership Data:
> >> > > > > > > Apache Commons was founded 2007-06-19 (17 years ago)
> >> > > > > > > There are currently 149 committers and 44 PMC members in
> this
> >> > > > project.
> >> > > > > > > The Committer-to-PMC ratio is roughly 5:2.
> >> > > > > >
> >> > > > > > Missing from this paragraph is the fact that Commons has
> enabled
> >> > > > > > universal commit.
> >> > > > > >
> >> > > > > > > Community changes, 

Re: [DRAFT] June Report to the Board

[sebb]

Note that moving the dependabot PR emails to a different list (if it's
even possible) is only part of the problem.
Applying the PR generates a message to the commits list (which cannot
safely be dropped) as well as a message closing the PR.

On Sat, 15 Jun 2024 at 21:03, Phil Steitz  wrote:
>
> On Sat, Jun 15, 2024 at 12:27 PM Gary Gregory 
> wrote:
>
> > Hm, would using GitHub Issues instead of Jira make the trail following
> > easier, harder, or the same?
> >
>
> Harder, because then you would have to search yet another place to
> reconstruct history.  But that would be less of an issue over time.  I
> don't see how it would make it better.  What bugs me is not so much having
> to look in multiple places as the degraded discussion.  We never had
> "roadblocks" before - just a convention that we use the dev list to talk
> about substantive issues.  JIRA (or Bugzilla or Github Issues or
> ) is for users to report bugs, ask for enhancements,
> organize work, mark things as done. etc.  commits@, github PR review,
> next_cool_review_board  is to enable review of proposed or committed code.
> The ML is for discussion.  Trying to force all discussion into PR "threads"
> has two big problems: 0) it lacks threading and unless we just drop dev@ it
> fragments discussion 1) it causes things to be discussed late.  It works
> great for trivial changes but for things that significantly change
> performance or behavior or where there are a lot of different ways they
> could be done, it is way better to actually talk about them rather than
> just hack a PR and try to collectively mutate it into something acceptable.
>
> Phil
>
> >
> > Gary
> >
> > On Sat, Jun 15, 2024, 2:58 PM Gary Gregory 
> > wrote:
> >
> > > If we want to have everything recorded in one place, then we need to put
> > > up some roadblocks to PRs, the Wiki, and Jira like ... what? Have a PR,
> > > wiki, and Jira template/gate that says... you must discuss your
> > > issue/bug/feature first on the mailing list? It does not feel workable.
> > >
> > > I don't think this is about people being dinosaurs, it's just the
> > > technology and processes that are changing. I really like working with
> > > GitHub PRs and GitHub CI builds. I don't want to go back to emails only
> > > just like don't ever want to use an IRC thing.
> > >
> > > Some people don't want to create a GitHub account, so it's Jira and diff
> > > files for them, but that's rare. BUT it gives us a LOT MORE work to
> > > validate a patch compared to GitHub CI where it can use many OSs and Java
> > > version while I'm sleeping :-)
> > >
> > > Gary
> > >
> > >
> > > On Sat, Jun 15, 2024, 2:00 PM Phil Steitz  wrote:
> > >
> > >> On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory 
> > >> wrote:
> > >>
> > >> > Note that it is 1) awkward to say "Let's stop talking about this PR in
> > >> > this PR"
> > >>
> > >>
> > >> Funny we used to do that all the time in Jira comments.  I guess times
> > >> change.  FWIW, I think it is a step backward in discussion and
> > ultimately
> > >> code and archive quality.  To me it is "awkward" to have to be
> > constantly
> > >> @somebody and not have threads or definitive discussion anywhere.  Works
> > >> fine for trivial changes but does not really work for substantive
> > >> discussion of bigger things.  So we end up never actually having those
> > >> discussions and there is no reasonably searchable archive of the thought
> > >> process that led to the changes going in.  We used to have that and it
> > was
> > >> a useful thing, especially for the more complex components.
> > >>
> > >> Phil
> > >>
> > >>
> > >>
> > >> > and 2) "You need to subscribe to a mailing to continue this
> > >> > chat." It's just hard to find when to ask for a switch. Especially
> > >> > when GH has a nice UI to make comments _about code_. Over at Log4j, we
> > >> > now use GitHub issues instead of Jira, furthering the split...
> > >> >
> > >> > Gary
> > >> >
> > >> > On Sat, Jun 15, 2024 at 12:38 PM Phil Steitz 
> > >> > wrote:
> > >> > >
> > >> > > On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory <
> > ggreg...@apache.org
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > > > On 2024/06/12 17:17:24 Phil Steitz wrote:
> > >> > > > > On Wed, Jun 12, 2024 at 7:27 AM sebb  wrote:
> > >> > > > >
> > >> > > > > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory <
> > >> ggreg...@apache.org
> > >> > >
> > >> > > > wrote:
> > >> > > > > > >
> > >> > > > > > > Hello All,
> > >> > > > > > >
> > >> > > > > > > Here is the draft of our board report for June I plan on
> > >> > submitting
> > >> > > > in a
> > >> > > > > > day or so, feedback is welcome.
> > >> > > > > > >
> > >> > > > > > > ## Description:
> > >> > > > > > > The mission of Apache Commons is the creation and
> > maintenance
> > >> of
> > >> > Java
> > >> > > > > > focused
> > >> > > > > > > reusable libraries and components
> > >> > > > > > >
> > >> > > > > > > ## Project Status:
> > >> > > > > > > Current project status: Ongoing with moderate