Shall we release 0.11 as 1.0 to signal maturity?

[pivovarit]

In one of the issues, @pertl brought up an important perspective that it would be beneficial to release 0.11 as 1.0 for the sake of:

importance of having a final version number as a prerequisite of acceptance especially in large enterprises

This is definitely something that we can do. That would mean that the last minor release of 0.x gets promoted to 1.0, and then the current work gets stashed into the 2.x stream.

What do you think?

Important context:

• the library is already production-ready and widely used
• we already had two major releases before the vavr rebrand

[domix]

As a long-time heavy user, I can certify that Vavr is mature enough to reach 1.0.

[geovannymcode]

As a long-time Java developer and Vavr user in production systems, I fully agree with this direction.

I’ve used Vavr in financial microservices (Java, reactive and event-driven architectures), where it has proven to be mature, stable, and reliable in real-world scenarios.

Promoting 0.11 to 1.0 would send a strong and positive signal, especially for enterprise adoption, where a final version number still matters a lot.

+1 for releasing 1.0 and continuing innovation towards 2.x.

[pivovarit]

That's my thinking as well - for a while, I was worried that people could be disappointed that 1.0.0 is not revolutionary... but it looks like everyone votes "yes". Let's do it then :)

[pivovarit]

Everyone involved voted yes - it's crystal clear what to do next. Thanks everyone, for your input!