Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release version 0.3.0 and 1.0.0 #120

Open
zuphilip opened this issue Jan 6, 2020 · 11 comments
Open

Release version 0.3.0 and 1.0.0 #120

zuphilip opened this issue Jan 6, 2020 · 11 comments
Milestone

Comments

@zuphilip
Copy link
Member

zuphilip commented Jan 6, 2020

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?

@zuphilip
Copy link
Member Author

zuphilip commented Jan 9, 2020

Can someone now make a release 0.3.0?

@stweil
Copy link
Member

stweil commented Jan 9, 2020

See https://github.com/UB-Mannheim/ocr-fileformat/releases/tag/v0.3.0.

@stweil stweil added this to the v1.0.0 milestone Jun 25, 2020
@stweil
Copy link
Member

stweil commented Jun 25, 2020

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.

@stweil
Copy link
Member

stweil commented Aug 31, 2020

As soon as PR #127 is merged, only support for GCV (issue #125) is missing for milestone v1.0.0.

@stweil
Copy link
Member

stweil commented Sep 18, 2020

A new release v0.4.0 is now available.

@stweil
Copy link
Member

stweil commented Aug 16, 2023

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?

@stweil
Copy link
Member

stweil commented Aug 16, 2023

I should ask @bertsky and @jmechnich, too, as both have also contributed significantly to this repository.

@jmechnich
Copy link
Contributor

I have no particular opinion about this...but closing an issue sounds great. 😺

@bertsky
Copy link
Contributor

bertsky commented Aug 16, 2023

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.

@stweil
Copy link
Member

stweil commented Aug 16, 2023

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.

@stweil
Copy link
Member

stweil commented Feb 13, 2024

I think it's time for a new release, but this list contains issues which I'd like to get fixed before tagging v0.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants