However, versioning in packages follows a logical process except with MS products where it is driven by marketing things, isn't it?

Sure... in reality the product is what matters most and that's perfect! congratulations for this big new milestone and I'm excited to start playing with it

I totally understand the interest in decoupling Aspire as a product from the rest of the .NET ecosystem, but was it really necessary to highlight that by changing the version from its original evolution? Did this really matter?

Honestly, I don't know how to feel about this reasoning

github.com/dotnet/aspir...

#dotnet @davidfowl.com

Typically, when I talk about burnout, it's mostly about identifying and preventing it. However, in this video, we'll take a bit of a spin on the topic as we look at overcoming burnout once you're already experiencing it.

Watch here:
https://www.youtube.com/watch?v=bLWTf2YfUPk

it's such a shame! so disrespectful

private projects are better handled there. Furthermore, from a purely project management perspective, everything surrounding boards there feels better. Finally, CI/CD is not the same (just different).

On the other hand, purely from a dev experience I see your point.

should there be a contest? honestly I like both but I see different contexts where to apply each

hey @guiferreira.me ! no worries, thanks for getting back as soon as you noticed!!

I understand then the point, however I would expect breaking changes in a major release, so no complain if they would have done it this way honestly.