I'd like to get the latest Mono 2.x version.
According to the official Mono release history page it is 2.10.9
According to what appears to be the official archive it is 2.11.4
However the latest modification date in the archive above for a 2.X release actually belongs to 2.10.12
There is no mentioned of the latter two versions in Mono's website (according to Google at least).
Any ideas what's going on?
I found this blog post that suggests 2.11.4 may be an Alpha release (see the comments). Perhaps the same is true for 2.10.12, and the latest stable version was indeed 2.10.9?
A similar questions arises for the latest version of MonoDevelop supporting Mono 2.X.
According to a Xamarin rep in their mailing list it is 2.8.6.5, but the GitHub release history shows 2.9.6, and the following link works: http://download.xamarin.com/monodevelop/Mac/MonoDevelop-2.9.5.dmg.
Is it again a case of an Alpha / Beta release ?
Mono 2.10.12 is the latest stable 2.x release (although 2.10.10, 2.10.11, and 2.10.12 were really just MacOS-specific releases, iirc).
Mono 2.11.x releases were previews for Mono 3.0.
The latest stable 2.x release of MonoDevelop was 2.8.6.5.
MonoDevelop 2.9.x releases were previews for 3.0.
At the time, we used the same version scheme as the Linux kernel for both Mono and MonoDevelop, where an even minor version meant stable and an odd minor version meant development/unstable/preview/alpha/whatever-you-want-to-call-it.
I think Mono still uses the same version scheme, but MonoDevelop no longer does (starting with 5.0). For example, MonoDevelop 5.1 is stable even though the minor version number is odd.
Related
I have a project that uses Python.Net for which I specify to customers that they need 'Python 3.6 or later'. However, when for example, Python 3.10 becomes the current default download from Python.org, does this mean that there will be a period of time where my applicaion won't work because Python.Net hasn't been updated to work with Python 3.10?
Or do I have to tell customers an upper bound value for the required Python verion?
That strongly depends on how are you distributing Python.NET.
If you are shipping Python.NET before 3.0 (3.0 has not been released yet) with your .NET app, it can only work with the specific python version it has been built for.
If you are asking users to install Python.NET using pip, I think it is possible to do it from source, in which case it should work with any Python 3.6+. You can check that by installing Python 3.10 preview and trying from there. Wheels of course are only built for existing python versions.
Python.NET 3.0 should be able to support future Python 3.x versions once released. But right now it is in flux, and the next release might take 6-12 months: many features are still being developed and/or reworked.
Redis release cycle page states
Support
Older versions are not supported as we try very hard to make the Redis API mostly backward compatible. Upgrading to newer versions is usually trivial.
For example, if the current stable release is 2.6.x, we accept bug reports and provide support >for the previous stable release (2.4.x), but not for older ones such as 2.2.x.
When 2.8 becomes the current stable release, the 2.6.x will be the oldest supported release.
Does this mean that currently supported versions are 6.0 (latest stable version 6.0.6) and 5.0 (previous stable version 5.0.9), and older versions such as (4.0.x, 3.2.x, 2.8.x) are not supported?
Thanks in advance.
What is the most reliable source to find the latest version number?
Is it github?
And if yes, which version should I take?
Right now, here is what I see:
Should I take the 1.0.2k?
But then 1.1.0d seems like it is more recent (if it follows semantic versioning). What do the letters actually mean?
Note: in my case this is to compile an openssl version with nginx.
Last time I picked (quite randomly) the version 1.0.2h which seemed the latest at the time.
So what is the process to follow to find the latest openssl version?
https://www.openssl.org/ shows which version are current and supported.
Currently there are two major versions in development: 1.1.0 and 1.0.2. 1.1.0 is newer and has more features. But due to the cleanups between 1.0.2 and 1.1.0 lots of undocumented API (i.e. things which never were an official API but got used anyway since no official API existed) got broken and not all software works or works stable with 1.1.0 yet. Also, 1.1.0 tends to introduce not only features but also bugs faster than 1.0.2 when looking at the release history. And with 1.1.0 the chance is higher that documented behavior changes even between patch releases.
Thus if you need the new features with 1.1.0 then go with it. If you prefer a more stable version with a smaller chance of bugs use 1.0.2. In all cases you should always use the latest patch release and keep using it if new patches get released or backport security patches.
I am trying to run my pharo2.0 application on CentoOS which was previously been installed in a mac. The original version is pharo2.0 so I need to run the same image CentoOS too, but I get an error which says this below :
/lib/libc.so.6: version `GLIBC_2.15' not found (required by xxxxx)
Should I be trying to upgrade the CentoOS and see if pharo2.0 works or port my whole application to a later version of pharo?
There is now a VM build especially for systems with an older libc version. In fact there is a build for Centos specifically (which has a slight variation in linkages from Debian), the latest version of which is permalinked here. See http://pharo.org/download#custom for more info.
I am trying to find release notes for mono versions 2.10.11 and 2.10.12 but cant seem to find them. The latest I can find is 2.10.9. http://www.mono-project.com/Release_Notes_Mono_2.10.9
Thanks
Mono updated to version 3.
See latest mono release notes:
http://www.mono-project.com/Release_Notes_Mono_3.0#New_in_Mono_3.0
Actual Mono version for MAC OS X, Windows and openSUSE is 3.2:
http://www.mono-project.com/Release_Notes_Mono_3.2