-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Cmdstan 2.23 release candidate #852
Comments
@wds15 @bbbales2 would you mind helping me expand the first line on reduce_sum? Also, do we have a simple example we can show to people that isnt too complex but has some speedup? |
Sure, I am happy to give a hand. I have some time tomorrow for this. What a release!!! |
Actually...we can point people to the intro Ben wrote which is a rewrite of an intro to Map rect. In addition we have Good Material in the Stan user guide already. That should both do it, I think. |
Oh yeah, forgot about that. That is more than enough. |
@serban-nicusor-toptal let me know when you make the release candidate tarballs so I can post the news. Thanks! |
Good morning @rok-cesnovar |
Thanks! Looks good. I updated the name to
The PDF of the cmdstan guide is missing but that is it. We have some stanc3 fixes lined up already that will need to be swaped for the final release. But I guess that is the easy thing to change. If there are no severe bugs in Math/Stan/Cmdstan that will hopefully be everything. |
cmdstan makefile task |
checking the CmdStan guide now - found broken links in the doc - fix in time for release? |
fwiw, RC builds on both High Sierra and Catalina - but my environments are relatively cruft-free - using XCode's toolchain, i.e., clang++ |
Yes, please. Feel free to tag for review. |
@rok-cesnovar - on ubuntu I got this error message while running makefile task
found this on SO - seems relevant - https://stackoverflow.com/questions/12230690/string-comparison-in-bash-not-found/12230723 this is used in two of the makefile files:
I think the logic that's triggering this message is only relevant for Windows - what do you think? |
@mitzimorris That may be because make is by default using |
@serban-nicusor-toptal would you mind doing a release candidate 2? We had to fix a few things and I think that would be best. So cmdstan develop + stanc3 nightly. I would say we move the actual release to Wednesday or Thursday to not prolong the feature freeze too much? |
Hey @rok-cesnovar you can find rc-2 here please let me know if everything is fine, thanks! |
Cmdstan release notes:
|
comment in above release notes, each entry should be capitalized and have a period at the end (i.e., a sentence) - or all entries should be lowercase with no period (i.e., a phrase) |
I will fix that in a sec. If anyone volunteers for making a post once released, please let me know. Else I will make one in the evening CET time. |
happy to start work on a post - we should also put an announcement up on Andrew's blog |
Hey, math 3.2.0 is done. Posting here to be sure that won't break anything and is intended. |
Thanks! Here are the relevant changes for stanc3 (there were quite a few bugfixes from RC1.
Great! Yes. this is due to the hotfixes we had to do the last time. This looks fine. |
@serban-nicusor-toptal - are the docs getting updated automatically as part of the release now? the reduce_sum case study links to the docs at the end. also, I think the 2_23 docs for the User's Guide will have a bunch of really great new content - checking now. |
I didn't tie it to the release but it's a button press away, I will do it after the stan and cmstan release. Will let you know when done so you can review. |
Update: The release for math, stan and cmdstan is done. I am currently waiting on:
I am sorry that it takes more than usual but there is a VERY high load on AWS and our machines get terminated randomly because they're bought as on-demand ( we are using spot instances, which are instances not in use put for 80-90% less ). |
Hey @mitzimorris docs have been generated again here PR can you please take a look and confirm Jenkins did everything all right then merge? Thank you! What Jenkins did can be found here PS: Added manual to cmdstan release! |
looks great - merged it! |
Everything works fine on the stan release thank you! |
checking 2_22 docs - don't see redirects to 2_23 - maybe it'll take a few minutes to refresh? |
Checking the logs I don't see any error popping so everything should be working fine. Maybe it's cached somewhere. How can I debug this, on what page should I see a redirect ? I can check in the repository to see if it's there. |
https://github.com/stan-dev/docs/blob/master/link_to_latest.py - this needs to be run on 2_22 but it's a destructive hack-and-a-half, so it shouldn't be run more than once. |
On 2.22? Did you mean 2.23? |
I understand you mean the I now understand what is wrong, will fix it in a PR in a second. |
Hey @mitzimorris please take a look at this PR it will fix the redirects. What happened ? Totally my mistake sorry, forgot to make Jenkins read the Jenkinsfile from the docs repository and it was using a static outdated version. Also found a typo, everything should be fine now! The job takes now an extra argument
|
looks great! |
Checked above links plus some extra, everything looks fine now. I have updated scripts and Jenkinsfile so next time it will work flawlessly. I think everything is done for the current release: If anyone has a few minutes it would help a lot to double-check, thank you! |
I updated 2 pages in the stan-dev.github.io repo to point to the 2.23 docs for Stan and CmdStan. don't know if this is worth automating. |
I'll do it now, better to offload this kind of stuff to automation. |
I think everything looks great. Thanks @serban-nicusor-toptal! |
Summary:
We are going to have a release candidate for this next release. Opening an issue to track everything about it.
@serban-nicusor-toptal can you make release candidate tarballs at the end of your work day? On the very unlikely chance something gets merged after that we will update tomorrow. But I doubt there will me much action. Once we have the release candidate tarballs ready and we can proceed I will make a post on Discourse for users to try it out.
Draft of the text that will go with the announcement:
Current Version:
v2.22
The text was updated successfully, but these errors were encountered: