Feedback Please add a "Production Ready" tag in addition to the "Preview" tag

If a package is out of preview, it should be reasonable to assume that it is production ready. But that is not always the case. It would be nice to have some other "Partial" tag that indicated it's in a nebulous in-between state, or a "Production Ready" tag to indicate its safe.

For example, the VFX Graph is fully implemented under HDRP but not SDRP. BUT UNTIL VERY RECENTLY the manual stated the following requirement: "Universal Render Pipeline (URP): Unity 2019.3 or newer." With 8.2.0 they added "The Visual Effect Graph is not out of preview with URP and so only supports a subset of platforms that URP supports. It also does not support every feature that is does with HDRP and also only supports unlit particles." It would be really nice if there were an easy way for users to know if a package were fully production ready and safe to use.

For bonus points, it would be great if you provided a link to release notes (known issues / change list / fix list) on a per package basis.

But the basic take-away is this. User's shouldn't have to scour forums in order to determine if something is production ready and safe to use.

 

Nothing is production ready in Unity for few years now, is only new broken half baked features and broken beyond repair old projects.

Unfortunately this is Unity these days, there is nothing there of good old stable reliable and powerful Unity, that was also easy to use and to program for.

I suppose they would just label all as production ready even if is half baked, as this is how they now think this term meaning is.

 

A change log is good. But no, I mean it would be nice to have a link to a bug/issues database on a per package basis. I'm sure you guys are using Jira or some equivalent. I'm just suggesting it would be nice to expose a read-only version of this on a per-package (or even a per-forum) basis. Let use evaluate if a package is stable enough to use or see if a bug has already been reported. Honestly, the "preview" tag seems somewhat arbitrary and not always sufficient. For example, like one one I gave, where a package might be deemed ready for HDRP (and thus out of preview) but have significant (and frequently not documented) non-parity on URP.

Right now, different packages seem very unaware of the unintended side-effects affect they are having on other packages. This is understandable to some extent with bleeding edge new feature, especially with "preview" packages. But what seems unacceptable to me is for users to have to manually perform a regression test across all features on the editor and all devices to see if there are unintended-side-effect integration issues every time you add/upgrade a package. Especially packages that are ostensibly out of "preview".

The documentation for new systems has been pretty sparse and forum support does not always happen. So you guys are our first line of defense in making sure its safe use/upgrade stuff.

But I love the direction the package system is going. Keep up the great work!

(Sorry for delayed response. Mini-crunch.)

 

Yes, please make a "production ready" tag, so you can then put it on nothing.

 

OK. Read the blog. Interesting take. I don't entirely agree this is the best course of action, but lacking transparency and documentation, maybe sweeping all the dirt under the rug is preferable.

It still doesn't address the issue of unintended side-effects and issues like URP/HDRP parity issues though (in regards to "non-preview" packages). Thanks again.