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

Clarify that 1.6.0-alpha36 is the current version #184

Open
fredZen opened this issue Dec 26, 2021 · 2 comments
Open

Clarify that 1.6.0-alpha36 is the current version #184

fredZen opened this issue Dec 26, 2021 · 2 comments

Comments

@fredZen
Copy link

fredZen commented Dec 26, 2021

Hi,

I spent a little while figuring out that I should probably be using oz 1.6.0-alpha36. What confused me was the fact that there are 2.0.0-alpha (up to 5) versions on clojars, compounded by the fact that all versions on clojars say that they were pushed from this years old git tree

I don’t know if the situation on clojars is easy to fix, but if it isn’t, perhaps a little note in the README could help? I’m happy to make a pull request for that if you’d like.

@metasoarous
Copy link
Owner

metasoarous commented Jan 6, 2022

Hi @fredZen. Thanks for asking about this.

Actually, 2.0.0-alpha5 is what I'd recommend using, unless something specific is broken for you, as it has quite a few new features and improvements (parallel evaluation of and markdown comment support for "namespace as a notebook" files, improved styles, better LaTeX support, etc). It is still alpha though (much more so than the 1.6.0-alpha* releases, which were actually pretty stable, but which I left in alpha, anticipating changes which might occur in implementing the afore described features; though I've taken quite a bit of care to break as little as possible). So if you find any problems with it, please raise an issue or reach out to me on the #oz channel on the Clojurians slack.

@metasoarous
Copy link
Owner

Oh; And yes, the git pointers are not up to date, since switching to deps.edn tooling. Unless there's a better way I'm not aware of, we'll have to write a little (babashka?) script that updates the pom.xml, and call it from the release task in the Makefile. I would absolutely appreciate help with that if you have some bandwidth. There's currently a bin/munge-provided-deps.clj bb script in the project, which is no longer needed, but which might serve as a nice starting point for solving the problem.

Thanks again!

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