[DRAFT][REPORT] December 2024 report to the board
Hi All, Here is the draft report: ## Description: The mission of Apache Commons is the creation and maintenance of Java focused reusable libraries and components ## Project Status: Current project status: Apache Commons is an ongoing project with moderate activity. Issues for the board: None. ## Membership Data: Apache Commons was founded 2007-06-19 (17 years ago). There are currently 150 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - Piotr Karwasz was added to the PMC on 2024-10-23 - No new committers. Last addition was Piotr Karwasz on 2024-08-27. ## Project Activity: Apache Commons continues to release components regularly. In this reporting period, we've released the following components: - DBCP-2.13.0 was released on 2024-12-02. - IO-2.18.0 was released on 2024-11-19. - RELEASE-PLUGIN-1.8.3 was released on 2024-11-09. - PARENT-78 was released on 2024-10-22. - PARENT-77 was released on 2024-10-09. - PARENT-76 was released on 2024-09-28. - CSV-1.12.0 was released on 2024-09-25. - IO-2.17.0 was released on 2024-09-18. - PARENT-75 was released on 2024-09-18. Further releases are planned. In general, we are still a Java 8 based project but continue to monitor the rate of adoption of Java versions to determine when we should update the platform requirement of each components. ## Community Health: The statics show that we have overall decreased activity but we have an increase in contributors. We welcomed Piotr Karwasz to the PMC this reporting period. We monitor Jira tickets and GitHub pull requests (PRs). We discuss PRs usually on GitHub and sometimes more generally on the dev mailing list when reaching a wider audience is needed in case not all members monitor GitHub PRs. We use Jira, not GitHub Issues. Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Lang] Method name (Was: [PR] Fb jpms - fixes for [...])
On Mon, 9 Dec 2024 at 15:19, Gilles Sadowski wrote: > > Hi. > > Following up here on the question on GH: > > > why is this disussion again NOT happening on any ASF list but here where it > > does not get reflected to any ASF list afaict? > > As Sebb wrote (below), the discussion is sent to "issues@". Subscribed > people can see what is discussed on GH but their eventual reply won't > be sent there, only to "issues@" (which doesn't do any good). > [That's why I started a thread on "dev@".] Note that JIRA updates are also sent to issues@. These can also contain some discussion, so developers should follow issues@ as well. > Gilles > > Le sam. 7 déc. 2024 à 18:05, sebb a écrit : > >> [...] > > - > 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: [Lang] Method name (Was: [PR] Fb jpms - fixes for [...])
Hi. Following up here on the question on GH: > why is this disussion again NOT happening on any ASF list but here where it > does not get reflected to any ASF list afaict? As Sebb wrote (below), the discussion is sent to "issues@". Subscribed people can see what is discussed on GH but their eventual reply won't be sent there, only to "issues@" (which doesn't do any good). [That's why I started a thread on "dev@".] Gilles Le sam. 7 déc. 2024 à 18:05, sebb a écrit : >> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[LANG] [DISCUSS] Java Modularity support in commons-lang3
Hi! I created a PR which aims to fix commons-lang behaviour which is broken since quite a few years. To be more precise: commons-lang doesn't fully support anything beyond Java8 due to not acknowledging the java module system (leading to InaccessibleObjectException). And no, adding --add-opens is NOT a viable solution for most developers! https://github.com/apache/commons-lang/pull/1328/ Yes, the comments seems to get reflected to issues@ but I'd like to discuss this on a broader level: Do we like to support anything beyond Java8 in commons-lang or not? It boils down to the fact that there are a few people who like to see commons-lang move forward, and others who want to stick to pre 2017 code. > Note that this PR is worse than I thought because we already have a feature > to bypass reflection! Use > `EqualsBuilder.setBypassReflectionClasses(List>)`. This is not really a viable solution for this very case. a) you'd have to add tons of classes all over again for each usage. We are talking about 30++ classes? For every usage... b) You'd need to do this extra miles when running with Java9++ in comparison to Java8. So you have to change user code when moving from one Java version to the other? That's stupid imo! c) try using this on a class which contains e.g. an ArrayList, a Set or a Map. It will e.g. use List#equals() which also does equals() on it's items (btw, I explained this to you already...). Which is NOT what users expect. Instead it should iterate over the List and use ReflectionEquals on the elements. This is exactly what the PR does (amongst other things). Let's face it: if commons-lang does not obey basic Java rules (in this case Java9++), it will be kicked out of projects down the road. And yes, I right now have this question whether to keep commons-lang in customer projects or replace it. That's the reason why I did invest a few days to provide suggestions for a way forward. We need to provide this functionality somehow. JIRA is full with respective tickets and bug reports (e.g. LANG-1685). And I don't care whether we change the existing code, duplicate the functionality over to a new package or even create commons-lang4. But being ignorant to the requirement to support Java9++ out of the box will make commons-lang go the way of the dodo, I fear. Happy to discuss the way HOW we move forward. But we should move forward. LieGrue, strub
Re: [Lang] Method name (Was: [PR] Fb jpms - fixes for [...])
Le lun. 9 déc. 2024 à 16:36, sebb a écrit :
>
> On Mon, 9 Dec 2024 at 15:19, Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Following up here on the question on GH:
> >
> > > why is this disussion again NOT happening on any ASF list but here where
> > > it does not get reflected to any ASF list afaict?
> >
> > As Sebb wrote (below), the discussion is sent to "issues@". Subscribed
> > people can see what is discussed on GH but their eventual reply won't
> > be sent there, only to "issues@" (which doesn't do any good).
> > [That's why I started a thread on "dev@".]
>
> Note that JIRA updates are also sent to issues@.
> These can also contain some discussion, so developers should follow
> issues@ as well.
Sure; but I think that the point is that some discussions should be
"manually" moved to here ("dev@") for non-trivial decision to be
validly made, because agreement or notice (either on JIRA or GH)
is not sufficient to assume that everyone would have agreed...
[Maybe this missing step is what caused the recent "surprise" on
added dependencies (?).]
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
