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? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
