Release v0.2.0?
See original GitHub issueI think we should create a new release. I started to draft one in GitHub, see https://github.com/UB-Mannheim/ocr-fileformat/releases . However, I am not sure, what has to been done with the release option in the Makefile. Is it enough to increase the version counter? Do you agree that we are now at v0.2.0
?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:13 (13 by maintainers)
Top Results From Across the Web
release v0.2.0 · antfu/strip-literal@8dc9d0b - GitHub
Strip comments and string literals from JavaScript code - release v0.2.0 · antfu/strip-literal@8dc9d0b.
Read more >v0.2.0 Release Notes
This release marks the start of support for the Pike release in Patrole. New Features¶. Add security groups and server security groups tests...
Read more >Announcing DoltLab v0.2.0 | DoltHub Blog
Today, we're excited to announce DoltLab's latest release v0.2.0 that contains fixes for all of the identified bugs and functionality ...
Read more >Release v0.2.0 | PipeCD
Release v0.2.0. Release v0.2.0. Monday, July 27, 2020. Changelog since v0.1.9. Notable Changes. No notable changes for this release ...
Read more >Release v0.2.0 - OpenFunction
benjaminhuo benjaminhuo released this on 2021.5.17 Release: v0.2.0 Release notes: Support OpenFunctionAsync serving runtime(backed by Dapr ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nevermind, I have just done it with the MIT: https://github.com/filak/hOCR-to-ALTO/commit/80ae1f9f2a0d1d5d54450b1f6592c5a82ee8561d
Yes, good point, I forgot the whole “code cleanup and backend rewrite” part. We can release that now and maybe schedule the outstanding merges in another issue.