Hi, Thank you for pitching in!
Keep in mind that feedback may be sporadic depending on various people's schedules and priorities ;-) Gary On Fri, Aug 25, 2023, 1:43 AM Buddhi De Silva <gbids...@gmail.com> wrote: > Thank you for your quick responses. > If I am summarizing the discussion for a quick conclusion for developers > who are looking to contribute, the following points can be concluded. > > 1. Bugs are safe to start work on because they are anyway bugs which we > need to look into. > 2. Issues marked with improvements and new feature requests may or may not > be accepted. Therefore, best to get a vote on them using the dev mailing > list. > > Feel free to comment / provide more feedback :) > > On Thu, 24 Aug 2023 at 17:21, Elliotte Rusty Harold <elh...@ibiblio.org> > wrote: > > > Java 8 is **not** EOL. It is fully supported by multiple vendors > > including Oracle, which has committed to supporting it indefinitely. > > Some JDK 8 downloads from Oracle are no longer available without a > > support contract. That's all. > > > > Java 8 is in common use at many organizations and in many projects. I > > no longer have access to industry wide metrics about JDK versions, but > > based on what I could see a year ago, I'm pretty confident JDK 8 will > > be with us through the end of the decade, and likely longer. > > > > When a bug or security issue is fixed in Apache Commons, clients > > should be able to quickly upgrade to a new release of the library > > without updating their JDK. This is critical for maintaining secure > > infrastructure. Maintenance and legacy code isn't as sexy as > > refactoring working code to use the latest > > super-happy-lambda-fun-time-absolutely-no-bugs-we-promise feature from > > Java 38 EA 17, but it's much more important for producing robust > > software that does the job it needs to do. > > > > On Thu, Aug 24, 2023 at 11:23 AM Gary Gregory <garydgreg...@gmail.com> > > wrote: > > > > > > IMO, requiring Java 11 is acceptable, Java 21 is around the corner and > > Java > > > 8 is EOL anyway. > > > > > > Gary > > > > > > On Thu, Aug 24, 2023, 6:34 AM Elliotte Rusty Harold < > elh...@ibiblio.org> > > > wrote: > > > > > > > On Thu, Aug 24, 2023 at 8:28 AM Buddhi De Silva <gbids...@gmail.com> > > > > wrote: > > > > > > > > > > HI Team, > > > > > > > > > > Also, some tickets contain the patch files > > > > > provided by the community and some of them seem to be accepted by > the > > > > > Apache CSV team but ticket status is Open and unresolved. > > > > > In this case, before I dig into some issues for possible fixes, I > > would > > > > > like to know whether all open issues in the CSV Jira board are > still > > > > valid > > > > > and planned to be integrated in the upcoming releases if we have > > possible > > > > > PRs. > > > > > > > > Almost certainly not. Just because some random dev files a feature > > > > request does not imply that anyone else, much less project > > > > maintainers, consider it a good idea. A lot of these should be > triaged > > > > but I'm not sure who has permissions to do that. > > > > > > > > If you're looking for something to work on, try to get consensus on > > > > the mailing list that a feature is a good idea before commencing > work. > > > > You could probably work on obvious bugs safely too. That is, anything > > > > where anyone who looks at it would immediately say, yeah, it';s not > > > > doing what the docs say it does. > > > > > > > > I would stay far away from any issue that suggests changing the API > > > > incompatibly or requiring JDK 11+. That's a non-starter. > > > > > > > > -- > > > > Elliotte Rusty Harold > > > > elh...@ibiblio.org > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >
