[
https://issues.apache.org/jira/browse/CSV-301?focusedWorklogId=800283&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-800283
]
ASF GitHub Bot logged work on CSV-301:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/22 11:27
Start Date: 12/Aug/22 11:27
Worklog Time Spent: 10m
Work Description: garydgregory commented on PR #250:
URL: https://github.com/apache/commons-csv/pull/250#issuecomment-1213011678
> Isn't it about time to release 2.0.0?
That's a different issue from this PR and more appropriate for the
developer's mailing list.
No one has asked for a major release that I am aware of. Usually, we release
a major release to break the API for new features. A major release to only drop
deprecated methods seems unnecessary (to me) for now.
My main concern is making sure the deprecated API remains the same and is
thoroughly tested. Maybe the code coverage action on GitHub is enough, I am not
sure, but it might be a good sign that it has not complained.
Let's see what others think.
Issue Time Tracking
-------------------
Worklog Id: (was: 800283)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
