Комментарии:
I know I'm the dumbest person in the room, but the 14 RCs aren't ready for anybody (developer or user). I don't know why HQ is so hell-bent on burning things down over a more iterative approach.
When I review the roadmap, I can't help but wonder about the logic behind HQ's commitment to releasing major versions on such distant dates. How can we be certain about the need for major versions due to breaking changes in the API? The frequent version releases seem to be causing significant discomfort for both the community and our internal teams.
In my opinion, a more flexible approach to backoffice changes could involve creating a standalone Nuget Package. This package could be implemented and used for Umbraco 10/13 right away, and when it's fully prepared, it could be integrated into a new major version, becoming the standard.
A good litmus test for whether something is actually a RC in a good place is COMPLETE documentation with code samples that work. I've found mounds of missing documentation and lines of wrong code in the past 24 hours.
I don't want this comment to be disheartening to the HQ team. I just want them to know that the quality of their releases is gradually declining. The approach could be more iterative. Their roadmap shouldn't be gung-ho on releasing versions and invalidating everybody's hard work "just because." A system that is supposed to be composable shouldn't require frequent and major updates to the underlying framework.
I'm very happy with the initiative and direction to move away from AngularJS and take a more FED approach to the backend UI/UX. Before, so much of it was C# or just better in C#. Moving away from AngularJS and embracing web standards and web components is a huge win, IMO.
/ I'll get off my soap-box now.
