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

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 add

[COLLECTIONS] documentation question

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

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 X

Re: [DRAFT] June Report to the Board

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 w

Re: [DRAFT] June Report to the Board

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 f

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

+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

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

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

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

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", vers

Re: [COLLECTIONS] documentation question

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 do

Re: [COLLECTIONS] documentation question

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 document

Re: [DRAFT] June Report to the Board

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

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

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 Pa

Re: [DRAFT] June Report to the Board

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 arch

Re: [DRAFT] June Report to the Board

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 thi

Re: [DRAFT] June Report to the Board

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? Ha

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

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 add

Re: [DRAFT] June Report to the Board

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

Re: [DRAFT] June Report to the Board

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