What _is_ up with v2.110?

Adam Wilson flyboynw at gmail.com
Fri Mar 7 00:47:50 UTC 2025


On Thursday, 6 March 2025 at 00:08:00 UTC, Quirin Schroll wrote:
> On Tuesday, 4 March 2025 at 23:08:37 UTC, Adam Wilson wrote:
>>> The project isn't viable if it can't release.
>>
>> Nobody says this about other languages despite them being on 
>> much longer release timelines. C++ is three years. Rust 
>> editions are three years. C# is yearly. Java is twice yearly.
>
> That is *language* version schedules, not *compiler* version 
> schedules. There are updates to MSVC around every few months.
>
>> In the grand scheme of things a yearly release cadence is 
>> actually pretty quick.
>
> For languages, yes. For compilers, no.

But that's exactly what I am talking about. MSVC gets 
regression/critical fixes monthly, standard bug fixes and 
features every 3 months, and ISO Standard upgrades every three 
years.

What I suggested isn't materially different. With the caveat that 
we're not an ISO standard so we get to choose our language 
feature release cadence.

We can do monthly point release for ice/regressions/critical 
fixes and then say 6 months for  features and standard bug fixes.




More information about the Digitalmars-d mailing list