Open zuphilip opened 4 years ago
Can someone now make a release 0.3.0?
Is there anything else we definitely want for a version 1.0.0 afterwards?
See milestone v1.0.0. Maybe other issues should be added there, too.
As soon as PR #127 is merged, only support for GCV (issue #125) is missing for milestone v1.0.0.
A new release v0.4.0 is now available.
Meanwhile the latest release (from November 2022) is v0.5.0.
Maybe it's time for a new release, either v0.6.0 or finally v1.0.0 (and close this issue then). What do you think, @kba and @zuphilip?
I should ask @bertsky and @jmechnich, too, as both have also contributed significantly to this repository.
I have no particular opinion about this...but closing an issue sounds great. :smiley_cat:
I'd recommend going through the open issues once more and deciding/labelling whether any of those are important enough to block a v1.0.
Perhaps Travis CI can be updated and extended (more roundtrip examples with recent converters, #114)?
Also, it looks like some issues are outdated.
Perhaps Travis CI can be updated and extended (more roundtrip examples with recent converters, #114)?
Thanks for noting this. Travis is no longer supported. I'll remove it and replace it by a GitHub action.
After merging PR #116 we should finally release version 0.3.0 and test it extensively and fix any occurring issues. Is there anything else we definitely want for a version 1.0.0 afterwards?