![]() I understand that there would be some testing that can happen during beta, but time and again it has shown that that's too late to actually fix workflow and design issues.Ĭlick to expand.I think the count of Unity developers and studios which will unhappy with these change will be more, the others which requested you about that change (many of them doesn't know about it now) Tying package versions to editor versions so strongly will only help beginners, who have less chances to mess up their projects everyone else is hurt by this because you're essentially saving "you're out of support if you're changing the package version, even if the old one is broken". You're essentially saving "We don't care if it's broken on release! Let us have a cleaner lifecycle!". ![]() ![]() It's a punch in the face for all people who have went the extra mile and reported alpha/beta/package issues. You are removing an essential and crucial part of testing - exposure to real-world projects - before code hits the general user population. You will confidently release packages that are broken for users, because no user had a chance to test them. I hope you understand that this will hurt the overall quality of the Unity product, not improve it. In any case, you can still edit manually the manifest.json of your project, but this is a scenario that can make the product unstable and so, we don't recommend to use unless you have no other options. New major/minor release version of built-in packages are only available through the release of a new Unity version and can update in older Unity versions, if we are confident enough that we can safely land these changes.Īny patch versions of these built-in packages can update the already verified versions and can be made available more directly through a package update from our official package registry. We need to make sure that our users can work safely. ![]() These packages (code editors integration) are even more critical for the stability of the product because they are allowed to run within the safe mode environment if something goes wrong with the compilation of your project. Starting with 2021.1 this is by design to ensure the quality of these built-in packages and the overall stability of the product.
0 Comments
Leave a Reply. |