Stan 2.19 release planned for Monday March 18th

Developers
41

I suspect this isn’t the correct place to request it (and if not, I would appreciate a pointer to where would be better!), but it would be very useful if the documentation contained information about the changes from previous versions (beyond the “deprecations” sections).

42

You can find that in the release notes on GitHub: https://github.com/stan-dev/stan/releases

43

Yes, but I suppose a more user-friendly version would also be useful since to actually understand this required looking back through commits, etc., whereas a list of bullet points with a little more detail in the text would probably satisfy most users in a form that would actually put the list of new possible tools/operations/functions right in front of us where we are already looking. I.e., this is actually important to “average” users who came to Stan at an earlier version, and it shouldn’t require navigating GitHub to get it.

On the other hand, I completely appreciate that this is an actual development burden I am requesting, and so appreciate that it is not high priority (or it would have been requested sooner).

44

I’ve asked the community to start creating more user-informative pull request titles going forward, which should help with that a bit. Maybe someone wants to volunteer to write up more detailed reports with a specific audience in mind - we’d be happy to add such a thing to the release notes. We only had one such thing so far (GPU intro by Erik).

1 Like
45

For the Math library, I’d prefer the issues to be clearly described. They should describe what the feature / bug is and the PR should describe how it’s being addressed (implementation details, design of code, etc.). In other words, the issues should be more user-facing, the pull requests should be more developer-facing.

46

That works too.

47

I think I don’t know that one. I’ve been looking for something like that. Where can it be found?

48

There’s no tutorial yet, just the release announcement earlier in this thread.

49

There was a performance bug with individual matrix element access in 2.19.0 (see this thread for details) On Thursday at 1pm NYC time I’ll do a full release with whatever commit last passed all of the tests up and down the repos, which will either be 2.20.0 or 2.19.1 depending on if we have new features or just bug fixes, respectively.

50

I guess this didn’t happen? Any new estimate for a release date?

51

We had 2.19.0 on March 20th and 2.19.1 on April 18th: https://github.com/stan-dev/cmdstan/releases Looks like both RStan and PyStan are behind.

2 Likes
52

I missed or forgot about 2.19.1.

Can we do a new release soon? There are two things which would be great to get in (for PyStan specifically):

53

The next release will be something like July 18th - in general, three months after the last release other than when we have major bugs.