We have historically made stable releases of Mono that get branched and maintained for long periods of time. During these long periods of time, we evolve our master release for some four to five months while we do major work on the branch. Historically, we have had done some of these large changes since we have rewritten or re-architected large parts of our JIT, or our garbage collector, or our compilers.There were points in the project history where it took us some 9 months to release: seven months of new development followed by two months of beta testing and fixing regressions. With Mono 2.6 we tried to change this, we tried to close the release time to at most six months, and we were relatively good at doing this with 2.8 and 2.10. We were on track to do a quick Mono 2.12 release roughly around May, but with the April bump in the road, this derailed our plans.Since 2.10.0 was released two things happened: On Master: plenty of feature work and bug fixing.
On our 2.10 branch: bug fixes and backporting fixes from master to 2.10 Now that things have settled at Xamarin and that we are getting Mono back into continuous integration builds we are going to release our first public beta of the upcoming Mono, it will be called Mono 2.11.1. We will keep it under QA until we are happy with the results and we will then release Mono 2.12 based on this. Read more: Personal blog of Miguel de Icaza
QR:
On our 2.10 branch: bug fixes and backporting fixes from master to 2.10 Now that things have settled at Xamarin and that we are getting Mono back into continuous integration builds we are going to release our first public beta of the upcoming Mono, it will be called Mono 2.11.1. We will keep it under QA until we are happy with the results and we will then release Mono 2.12 based on this. Read more: Personal blog of Miguel de Icaza
QR: