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

Update ocrd_olena, tesseract, ocrd_cis #104

Merged
merged 1 commit into from
May 31, 2020
Merged

Update ocrd_olena, tesseract, ocrd_cis #104

merged 1 commit into from
May 31, 2020

Conversation

kba
Copy link
Member

@kba kba commented May 31, 2020

Update:

  • ocrd_olena: e000f24 (1.1.7)
  • tesseract: 62eae84
  • ocrd_cis: a6a2ecd
  • ocrd_tesserocr: 9d2253e (0.8.3 +1)
  • sbb_textline_detector: 3593506
  • workflow-configuration: 403ef75

Added:

  • CHANGELOG.md to track changes

Update:

  * `ocrd_olena`: e000f24 (1.1.7)
  * `tesseract`: 62eae84
  * `ocrd_cis`: a6a2ecd
  * `ocrd_tesserocr`: 9d2253e (0.8.3 +1)
  * `sbb_textline_detector`: 3593506
  * `workflow-configuration`: 403ef75

Added:

  * `CHANGELOG.md` to track changes
Copy link
Collaborator

@stweil stweil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should discuss the content of CHANGELOG.md (do we really want to duplicate information which is part of the git history?) and how often it gets updated (I prefer to update it only for releases).

@stweil stweil merged commit 3c097f0 into master May 31, 2020
@stweil stweil deleted the update-2020-05-31 branch May 31, 2020 15:40
@kba
Copy link
Member Author

kba commented May 31, 2020

I think we should discuss the content of CHANGELOG.md

Totally, this is just a proposal and the format is not that useful (I was mostly curious whether GitHub would be able to identify the short commit strings to the commits in the submodule).

I'm also well aware of #101 and thinking about a compromise. In the meantime, starting with a CHANGELOG seemed constructive but is not meant to preempt a proper solution to #101.

@M3ssman M3ssman mentioned this pull request Jun 2, 2020
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

Successfully merging this pull request may close these issues.

2 participants