[
https://issues.apache.org/jira/browse/CSV-301?focusedWorklogId=800446&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800446
]
ASF GitHub Bot logged work on CSV-301:
--------------------------------------
Author: ASF GitHub Bot
Created on: 13/Aug/22 23:02
Start Date: 13/Aug/22 23:02
Worklog Time Spent: 10m
Work Description: kinow commented on PR #250:
URL: https://github.com/apache/commons-csv/pull/250#issuecomment-1214243111
> Having more frequent releases (a couple per year) would be desirable for
this project as it would be for most libraries imo.
Agreed! Unfortunately we are a little restricted on developer-bandwidth. But
if you are willing to volunteer pushing some work for 2.0.0, that'd be really
helpful!
>-1 for now, because, we MUST test all existing Commons CSV APIs. I do not
think we want to write new tests that only test deprecated APIs.
@sman-81 I think a 2.0.0 release would be great, but we probably would have
to start reviewing issues in JIRA, existing pull requests, and the status of
the code base (e.g. do we need to bump java version for any good reason [we
normally avoid unnecessary minimum JVM bumps], is there anything useful in
existing CSV libraries that would be worth discussing adding in 2.0.0, etc.)
I agree we must not remove tests based on deprecation warnings, as they can
still be useful. I also agree that deprecation warnings can be demotivating to
contributors, and even to long-time maintainers/developers. I use Eclipse &
IntelliJ, and I always crave to have as little warnings as I can.
But I think in Eclipse & IntelliJ we should be able to suppress the warnings
for now, while we work on a 2.0.0 release. WDYT @sman-81 ?
We do not need to close this PR, if you'd like. Maybe make it a draft?
@garydgregory I think you have a lot more experience with the CSV code base
& maintaining the component. Do you think, if we fix existing issues in JIRA,
review the PR's, and remove deprecated API, we could prepare a 2.0.0 release? I
know we have a longer time to release major releases, but one or two major
releases per year doesn't sound too bad IMO. WDYT?
Issue Time Tracking
-------------------
Worklog Id: (was: 800446)
Time Spent: 1h 10m (was: 1h)
> Fix deprecation warnings in unit tests
> --------------------------------------
>
> Key: CSV-301
> URL: https://issues.apache.org/jira/browse/CSV-301
> Project: Commons CSV
> Issue Type: Improvement
> Affects Versions: 1.9.0
> Reporter: Markus Spann
> Priority: Trivial
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Fix deprecation warnings in unit tests of the project.
> The project has a large number of deprecation warnings in unit tests. Use
> updated API in these tests.
> Tests should keep up-to-date with the API, they often serve as a blueprint
> for how to use functionality.
> I will provide a pull request shortly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
