You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Currently bokeh-scala's version number is unrelated to bokeh's version, so in fact two versions have to be carried along. Maybe we should switch to something like bokeh's_version-rN, where N would be an integer, e.g. for bokeh 0.7.1, this would be bokeh-scala 0.7.1-r3 (r3, because 0.3 is the version in the current scheme). One thing we shouldn't do is to make bokeh's and bokeh-scala's version exactly the same, because it should be possible to release bokeh-scala (e.g. with bugfixes exclusively related to Scala) in between bokeh's releases.
The text was updated successfully, but these errors were encountered:
First off, great job here! I was also wondering about this versioning system. Any idea if the latest bokeh-scala is still fine with the bokeh release 0.11.* ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently bokeh-scala's version number is unrelated to bokeh's version, so in fact two versions have to be carried along. Maybe we should switch to something like
bokeh's_version-rN
, whereN
would be an integer, e.g. for bokeh 0.7.1, this would be bokeh-scala 0.7.1-r3 (r3, because 0.3 is the version in the current scheme). One thing we shouldn't do is to make bokeh's and bokeh-scala's version exactly the same, because it should be possible to release bokeh-scala (e.g. with bugfixes exclusively related to Scala) in between bokeh's releases.The text was updated successfully, but these errors were encountered: