中文天堂www在线资源,国产超级乱淫视频播放免费,一级a一级视频免费观看

After developing a package to the point where it is ready for Unity users to test it and provide feedback, a package enters the preview state. Packages in this state usually appear in the Unity Editor with the label and often usepreviewas part of their version.

注意：
In addition to the preview packages that are discoverable in the Package Manager window, there are some preview packages that are on Unity’s package registry server but don’t appear in the Unity Registry context. These packages are not discoverable in the Package Manager window because: - They are considered to be somewhat experimental, and therefore too risky to use in production. Some of these packages require a lot of training and expertise and are therefore recommended only in specific circumstances. - They are support packages, meaning that you shouldn’t use them on their own because they are designed to provide shared or additional functionality to existing packages. Undiscoverable packages can still appear in the Package Manager window if they were previously installed in your project. However, they are hidden so that users don’t discover them by accident and use them without realizing the risks.

注意：

In addition to the preview packages that are discoverable in the Package Manager window, there are some preview packages that are on Unity’s package registry server but don’t appear in the Unity Registry context. These packages are not discoverable in the Package Manager window because: - They are considered to be somewhat experimental, and therefore too risky to use in production. Some of these packages require a lot of training and expertise and are therefore recommended only in specific circumstances. - They are support packages, meaning that you shouldn’t use them on their own because they are designed to provide shared or additional functionality to existing packages. Undiscoverable packages can still appear in the Package Manager window if they were previously installed in your project. However, they are hidden so that users don’t discover them by accident and use them without realizing the risks.

Unity’s release management only grants a package the verified status after it passes several testing stages and validation procedures, which also include checks for appropriate documentation, changelog, and license files. Packages in this state may appear in the Unity Editor with the label and never use preview as part of their version.

If the package developer introduces changing or breaking changes to a package (either by introducing a change that breaks an API or affects its usage), that package returns to the preview state and the Package Manager does not suggest the new preview package as a possible update for the verified version.

![Unity Package Manager 中的包生命周期]![]Unity Package Manager 中的包生命周期

These states match where the package is in the development cycle:

狀態(tài)	描述
開發(fā)中 (In Development)	包開發(fā)者創(chuàng)建包。通常，這相當于將包嵌入到開發(fā)者的項目中。
預覽 (Preview)	When the package is ready for testing, the Unity package developer makes sure there is some basic test coverage, and that the package passes testing with the package validation suite. The package also needs at least preliminary documentation, an updated changelog, and licensing before the Unity package developer can apply to publish the package on Unity’s official package registry. At this point, the package is available for testing, so that any eligible Unity user can provide the developer with feedback. Most packages are available to any Unity users, although a few packages are limited to Unity IDs with specific entitlements. Preview packages can go through many changes before they are ready to be verified for a specific version of Unity. At some point in the future, they might pass the verification requirements; however, they might also be deprecated instead. Because there is no guarantee for future support, you should not use preview packages in production. For a list of preview packages available for this version, see Preview packages.
已驗證 (Verified)	該包已經(jīng)過嚴格的測試，通過了驗證并可以安全地在特定 Unity 版本上使用，也可以和其他已針對同一版本進行了驗證的包一起使用。此狀態(tài)僅適用于 Unity 內(nèi)部開發(fā)的包。對于第三方的包，請與相應的開發(fā)者聯(lián)系，以詢問有關其特定流程的信息。當某個包針對某一 Unity 版本經(jīng)過驗證后，Unity 保證在該 Unity 版本的存續(xù)期間支持這個經(jīng)驗證的包（在整個長期支持周期內(nèi)），并且不允許進行任何主要或次要更新（即，那些會破壞或更改 API 的更改）。對于每個新的 Unity 版本，每個已驗證的包都必須再次經(jīng)歷驗證過程，然后 Package Manager 才將其視為已驗證。要查看已針對此 Unity 版本驗證過的包列表，請參閱已驗證包。注意：有些包既不是已驗證的包，也不是預覽包。在許多情況下，這是因為包在 Unity 的之前版本中進行了驗證，但尚未針對當前版本完成驗證過程。有些包已發(fā)布到 Unity Package Manager 注冊表是因為它們被認為可以安全使用，但實際上從未經(jīng)過驗證。在上述兩種情況下，這些包在實際生產(chǎn)中都可以安全使用。

The Package Manager window displays a tag that corresponds to some of these states.

Unity Package stases and lifecycle

推薦文章

推薦教程

推薦課程