We only have the resources/bandwidth to author detailed release notes retrospectively on full releases. Dev builds are and are often initiated spontaneously (sometimes several a day) to support and develop our build and test infrastructure. We make them available as a (potentially) useful convenience to users, but they are not planned more than a few days in advance, and are not supported.
There is always a "next" milestone on GH that may be useful, e.g.:
We make a best-effort to populate these milestones after full releases, however contributors can and often do choose to work on quick or unforeseen "issues of opportunity" that are important to them or their own projects, and these are simply added to the milestone after they are completed. Additionally, we also welcome contributions from new contributors, and these are generally unpredictable in advance.
We are still experimenting with the information architecture of the docs site. There is a "roadmap" that is linked from the footer of every page, but it is probably easy to overlook. It links to:
I'm afraid it is only a very high-level to-do at this point, but I hope to make a pass over it sometime in the near future.
We have made recent strides to increase any relevant "migration notes" in full release notes. There are still important features and fixes that may necessitate changes, but we do consider them, and make efforts to minimize them or smooth any transitions, especially as the user base grows. I will also state that one of our requirements for a "1.0" release (that we hope to reach later this year) is to maintain APIs under test, which will also allow us to apply some level of automation to this kind of change reporting, and to adhere to a semantic versioning scheme.
I recognize that some of these answers may not seem ideal. However, the development of Bokeh principally relies on the generous (but not unlimited) support of one company, plus any additional community contributors motivated enough to get involved at a high level. Encouragingly, there are more and more new contributors, and I hope that we can grow the group of Bokeh core developers even more in the coming months. But still, there is nothing analogous to the Django Software Foundation to directly support and nurture the long-term course of the project. We do intend to apply to become a NumFocus Sponsored Project as soon as is feasible. This will make the long-term community governance clearly visible, as well as make it possible to accept financial donations from anyone interested in directly supporting the Bokeh team to be able to do more.
On Apr 2, 2016, at 5:11 AM, Andy Baker <[email protected]> wrote:
I'm fairly new to Bokeh and I'm struggling to find the 0.12 changelog or release notes or whatnot. I was hoping to see a list of what's new for both dev5 and 0.12 in general - and ideally links to the docs for new features where they exist.
Something similar to Django's release notes: https://docs.djangoproject.com/en/dev/releases/1.10/
As far as I can tell this page: http://bokeh.pydata.org/en/dev/ is just the latest full docs and I have no idea how to see what's changed. Even the link in the top menu to 'releases' only covers previous releases and not dev or beta versions.
I find release notes for new versions a great way to get a feel for the velocity and direction of a project hence my interest.
Apologies if I'm being dim but I've exhausted my google-fu trying to find something
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/73038923-40db-4038-b19a-51930a216cb8%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.