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

New release? #83

Closed
kloczek opened this issue Mar 3, 2020 · 2 comments
Closed

New release? #83

kloczek opened this issue Mar 3, 2020 · 2 comments

Comments

@kloczek
Copy link

kloczek commented Mar 3, 2020

I think that it would be good to flush currently committed changes and make new release :)

Looks like already at least few distributions are no longer using regular 1.5.0.

@nayuki
Copy link
Owner

nayuki commented Mar 5, 2020

Thanks, that's a good idea. I hesitated because I didn't make functional changes since v1.5.0. But it looks like I did a lot of work since then. Upon reviewing my series of commits, these are the main things I did:

  • Clarified a lot of internal code (especially for Rust, C++, and C).
  • Merged the C++ source files from 3 pairs to just 1 pair.
  • Modified internal assertions (which should not trigger unless I made a mistake).
  • Deleted JavaScript in favor of TypeScript.
  • Made very minimal changes to Java and Python source codes.

Given the same inputs, the libraries as of latest (commit 13a2558) still generate the exact same output as v1.5.0. Also, I keep master stable, so any project that took a non-tagged commit from my project is okay and not risky.

@nayuki
Copy link
Owner

nayuki commented Mar 5, 2020

All done. Posted v1.6.0 to PyPI (Python), crates.io (Rust), and Maven Central (Java).

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

2 participants