The following page has packages for version 3.6.3.
This version is quite old, and does not include major compatibility fixes, like this one . In my opinion, people running the 3.6.3 version will quickly encounter issues that are not present in the 3.7 branch.The 3.7 branch is, I think, stable enough to be released (last patch in 2010), unless of course if there are majors bugs I’m not aware of.
I think it would be for the best to build and package the 3.7 branch, and to advertise that version as the latest stable (instead of 3.6.3).
Or maybe to skip 3.7 and go to 3.8 directly, branched from master (it seems other useful improvement have been made too).
Or to change the page to remove packaged versions, and ask users to build latest version from master. But I think most people are reluctant to tie productions servers to a master’s latest commit. So the sensible way for users right now is to build versions from specific hand picked commits, or from forks. And this is not very user friendly.
Thanks in advance.