{"_id":"com.unity.dataflowgraph","name":"com.unity.dataflowgraph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","provider":"upm","versions":{"0.19.0-preview.7":{"_id":"com.unity.dataflowgraph@0.19.0-preview.7","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.19.0-preview.7.tgz","unity":"2020.1","upmCi":{"footprint":"a0225f69e55b46afc145db7e863c4a1717c7db8b"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.4 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"ae70ef287c371ebfe4f30262ec94de29ea9606ef"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.19.0-preview.7","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.8.0-preview.23","com.unity.burst":"1.4.1","com.unity.entities":"0.17.0-preview.41","com.unity.collections":"0.15.0-preview.21","com.unity.mathematics":"1.2.1"},"dist":{"shasum":"4810e96367c0baeacddc96eb4b58cfdc3a0148da","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.19.0-preview.7.tgz"}},"0.18.0-preview.3":{"_id":"com.unity.dataflowgraph@0.18.0-preview.3","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.18.0-preview.3.tgz","unity":"2020.1","upmCi":{"footprint":"faf80559d6e1e3c3f877f6c47a12d862f7922546"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.4 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"51f8ca0871a6c7c6bff7290f5b8ef269fdbdb945"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.18.0-preview.3","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.7.0-preview.17","com.unity.burst":"1.3.7","com.unity.entities":"0.16.0-preview.21","com.unity.collections":"0.14.0-preview.16","com.unity.mathematics":"1.2.1"},"dist":{"shasum":"cd1630a1df3171f4c9673f9d9057ea86e549fe83","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.18.0-preview.3.tgz"}},"0.17.0-preview.4":{"_id":"com.unity.dataflowgraph@0.17.0-preview.4","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.17.0-preview.4.tgz","unity":"2019.4","upmCi":{"footprint":"da658e338c600c0a3104279cc38a841b41ada74e"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.4 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"eb6ae607477c01e36991f1fbff1c18d392563f62"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.17.0-preview.4","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.10-preview.12","com.unity.burst":"1.3.0","com.unity.entities":"0.11.1-preview.4","com.unity.collections":"0.9.0-preview.6","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"d0cefc2789d31e27a0749ec70de3ac9d11ddab88","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.17.0-preview.4.tgz"}},"0.16.0-preview.3":{"_id":"com.unity.dataflowgraph@0.16.0-preview.3","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.16.0-preview.3.tgz","unity":"2019.4","upmCi":{"footprint":"80771ce13641ea82afa9968bea54409fa49e8bf1"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.4 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"a55cc8f1a77f0457882e742135b1ca9128270d07"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.16.0-preview.3","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.10-preview.12","com.unity.burst":"1.3.0","com.unity.entities":"0.11.1-preview.4","com.unity.collections":"0.9.0-preview.6","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"dc1df9a7efc24462429d8bbc90d7aebffadfb0ed","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.16.0-preview.3.tgz"}},"0.16.0-preview.2":{"_id":"com.unity.dataflowgraph@0.16.0-preview.2","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","unity":"2019.4","upmCi":{"footprint":"68d9139ab67abdc7d1a5ca5903e9882bd8230bde"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.4 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_npmUser":{},"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"64b87d8a6451ca12d3389382df6fb6d098091adb"},"_npmVersion":"5.6.0","_nodeVersion":"8.11.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.16.0-preview.2","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.10-preview.12","com.unity.burst":"1.3.0","com.unity.entities":"0.11.1-preview.4","com.unity.collections":"0.9.0-preview.6","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"7f4a2d803ed733dfd4dde2d40a5050df395ca3ef","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.16.0-preview.2.tgz"}},"0.15.0-preview.5":{"_id":"com.unity.dataflowgraph@0.15.0-preview.5","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.15.0-preview.5.tgz","unity":"2019.3","upmCi":{"footprint":"6f6df40a7a92784aa50fd828a314922be31c9e2f"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.3 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"4a064d816ed8d3dd66267cae427e40d76cb5b462"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.15.0-preview.5","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.10-preview.12","com.unity.burst":"1.3.0","com.unity.entities":"0.11.1-preview.4","com.unity.collections":"0.9.0-preview.6","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"a90407a5d54093b3d5e42724d035f6aee8465487","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.15.0-preview.5.tgz"}},"0.15.0-preview.4":{"_id":"com.unity.dataflowgraph@0.15.0-preview.4","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.15.0-preview.4.tgz","unity":"2019.3","upmCi":{"footprint":"b993876ff11a050ede519b7908c898d9dfc06154"},"readme":"# Instructions\nUsing this package is quite simple:\n- Start a fresh new Unity project in 2019.3 or later\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\n- Click the \"**+**\" drop-down menu in the upper left corner.\n- Choose \"Add package from git URL...\".\n- Type in \"com.unity.dataflowgraph\" and press Enter.\n\n\n# Where to Start\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\n\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\n\n\n# Repository CI summary - master\n\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\n\n# Bleeding edge / staging summary\n\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"9177f887d18cdcff219448a3b952f693e564e143"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.15.0-preview.4","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.10-preview.11","com.unity.burst":"1.3.0-preview.12","com.unity.entities":"0.11.0-preview.7","com.unity.collections":"0.9.0-preview.5","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"b2c1b5bc0cd4c4f711f74cc4ff63f3f5af644243","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.15.0-preview.4.tgz"}},"0.14.0-preview.2":{"_id":"com.unity.dataflowgraph@0.14.0-preview.2","bugs":{"url":"https://github.com/Unity-Technologies/com.unity.dataflowgraph/issues"},"type":"asset","_from":"file:com.unity.dataflowgraph-0.14.0-preview.2.tgz","unity":"2019.3","upmCi":{"footprint":"ade051676df927dac034b7ee4b1a0d210916a8c6"},"readme":"# Instructions\r\nUsing this package is quite simple:\r\n- Start a fresh new Unity project in 2019.3 or later\r\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\r\n- Click the \"**+**\" drop-down menu in the upper left corner.\r\n- Choose \"Add package from git URL...\".\r\n- Type in \"com.unity.dataflowgraph\" and press Enter.\r\n\r\n\r\n# Where to Start\r\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\r\n\r\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\r\n\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badge-proxy.cds.internal.unity3d.com/ca7c20e0-3c07-4e66-b844-ee960321c492)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/a115094e-0607-4291-961b-0369b1d01c1f)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/fad5393d-b64e-45f2-b171-585cf071c4c1)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/9dd544bb-024e-4d0d-91e4-48b5351ab797) ![ReleaseBadge](https://badge-proxy.cds.internal.unity3d.com/32c53de8-370c-4f83-a5ae-2f5ea9a8c3a5)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badge-proxy.cds.internal.unity3d.com/7780abaa-0c8b-491c-8f1f-414f6a7ebd82)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging&testWorkflow=package-isolation) [![](https://badge-proxy.cds.internal.unity3d.com/b3715519-4895-4ee1-ba35-bc570b9f1318)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging&testWorkflow=updated-dependencies) [![](https://badge-proxy.cds.internal.unity3d.com/c80b6eaa-9406-473d-87a0-0ee2502c3449)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badge-proxy.cds.internal.unity3d.com/b046a300-c3e4-4786-a407-367c00b7cf72)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"homepage":"https://github.com/Unity-Technologies/com.unity.dataflowgraph#readme","_resolved":"","_integrity":"","repository":{"url":"git+https://github.com/Unity-Technologies/com.unity.dataflowgraph.git","type":"git","revision":"6cd676570db2f40f63e5548ae24f6c665fa7b9c2"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.14.0-preview.2","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.8-preview.3","com.unity.burst":"1.3.0-preview.7","com.unity.entities":"0.9.1-preview.15","com.unity.collections":"0.7.1-preview.3","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"a1e90b497a16481007a13d82523c8e3724d9cea4","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.14.0-preview.2.tgz"}},"0.14.0-preview.1":{"_id":"com.unity.dataflowgraph@0.14.0-preview.1","type":"asset","_from":"file:com.unity.dataflowgraph-0.14.0-preview.1.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n- Start a fresh new Unity project in 2019.3 or later\r\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\r\n- Click the \"**+**\" drop-down menu in the upper left corner.\r\n- Choose \"Add package from git URL...\".\r\n- Type in \"com.unity.dataflowgraph\" and press Enter.\r\n\r\n\r\n# Where to Start\r\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\r\n\r\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\r\n\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/release-badge.svg) ![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/candidates-badge.svg)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_resolved":"","_integrity":"","repository":{"url":"https://github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git","type":"git","revision":"743d2b0ea51021effbd1577a137cbecaab4a14af","footprint":"77e8c55e97faba01fe644df0937c2cf9d9d34d28"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.14.0-preview.1","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.8-preview.3","com.unity.burst":"1.3.0-preview.7","com.unity.entities":"0.9.1-preview.15","com.unity.collections":"0.7.1-preview.3","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"6c14959d123486be274cdfafa55cc09e292252d4","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.14.0-preview.1.tgz"}},"0.13.0-preview.3":{"_id":"com.unity.dataflowgraph@0.13.0-preview.3","type":"asset","_from":"file:com.unity.dataflowgraph-0.13.0-preview.3.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n- Start a fresh new Unity project in 2019.3 or later\r\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\r\n- Click the \"**+**\" drop-down menu in the upper left corner.\r\n- Choose \"Add package from git URL...\".\r\n- Type in \"com.unity.dataflowgraph\" and press Enter.\r\n\r\n\r\n# Where to Start\r\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\r\n\r\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\r\n\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/release-badge.svg) ![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/candidates-badge.svg)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_resolved":"","_integrity":"","repository":{"url":"https://github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git","type":"git","revision":"042bc5edf851d52ab845ef709e37754a8c96871e","footprint":"c1e914b8ba7ede2b0284d2100d0aa4209f1213a0"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.13.0-preview.3","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.7-preview.11","com.unity.burst":"1.3.0-preview.6","com.unity.entities":"0.8.0-preview.8","com.unity.collections":"0.7.0-preview.2","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"1b5b42ba6f0eb15862a7d4d7e74f271ff46efc42","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.13.0-preview.3.tgz"}},"0.13.0-preview.2":{"_id":"com.unity.dataflowgraph@0.13.0-preview.2","type":"asset","_from":"file:com.unity.dataflowgraph-0.13.0-preview.2.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n- Start a fresh new Unity project in 2019.3 or later\r\n- Open the [Package Manager](https://docs.unity3d.com/Packages/com.unity.package-manager-ui@latest/index.html) window.\r\n- Click the \"**+**\" drop-down menu in the upper left corner.\r\n- Choose \"Add package from git URL...\".\r\n- Type in \"com.unity.dataflowgraph\" and press Enter.\r\n\r\n\r\n# Where to Start\r\nThe best resource for getting started are the Samples included with the package.  These are available through the Package Manager UI by selecting DataFlowGraph and scrolling to the bottom of its description.  There you will find options to import the \"Guided Tour in Code\" as well as some simple \"Examples\".\r\n\r\nAs of now there is very little formal high level documentation, however, all APIs are fully documented and most features are covered in the aforementioned \"Guided Tour in Code\".  The documentation is available through the Package Manager UI by selecting DataFlowGraph and clicking \"View documentation\".\r\n\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/release-badge.svg) ![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/candidates-badge.svg)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_resolved":"","_integrity":"","repository":{"url":"https://github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git","type":"git","revision":"32da8b628740f699dd041710ac359c1df3cdb3d4","footprint":"27dcafd840a44e6dfb0090447dafa26d9a2d3707"},"_npmVersion":"6.13.4","_nodeVersion":"12.16.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.13.0-preview.2","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.7-preview.11","com.unity.burst":"1.3.0-preview.6","com.unity.entities":"0.8.0-preview.8","com.unity.collections":"0.7.0-preview.2","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"392bd24e55e7ff5eb3ccb6985681176b49ef39ab","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.13.0-preview.2.tgz"}},"0.12.0-preview.7":{"_id":"com.unity.dataflowgraph@0.12.0-preview.7","type":"asset","_from":"file:com.unity.dataflowgraph-0.12.0-preview.7.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n\r\n- Start a fresh new Unity project\r\n- Change Player Settings for `Scripting Runtime Version` to `.NET 4.x Equivalent`\r\n- Change Player Settings for `Api Compatiblity Level` to `.NET 4.x`\r\n- Add in the DataFlowGraph package\r\n\r\nYou have __four options__ for that last step:\r\n1. Easy per project package installation\r\n    - Clone this repo to the `Packages/` sub-folder within your Unity project\r\n    - (you don't even need to restart Unity!)\r\n\r\n2. Shared package installation (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine\r\n   - From the PackageManager window, clik the + icon in the bottom of the left column to \"Add package from disk...\"\r\n   - Navigate to the cloned repo and select the package.json file\r\n\r\n3. Shared package installation option 2 (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine (ideally in a folder immediately adjacent to your Unity project folder)\r\n   - Quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"file:../../com.unity.dataflowgraph\"`\r\n\r\n4. Direct link to GitHub repo (does __NOT__ allow for DataFlowGraph framework development)\r\n   - First quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"ssh://git@github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git#master\"`\r\n   - The \"#master\" part can be replaced which any branch name in the DataFlowGraph package repo, or, any specific commit hash.\r\n     Furthermore it can be updated live while Unity is running.\r\n\r\nIn all cases above, if you want to be able to run the DataFlowGraph tests within the TestRunner, also add the following to `manifest.json` after the `dependencies` section:\r\n```\r\n     \"testables\": [\r\n        \"com.unity.dataflowgraph\"\r\n     ]\r\n```\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/release-badge.svg) ![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/candidates-badge.svg)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n\r\n#\r\n\r\n#\r\n\r\n#\r\n\r\n\r\n# UPM Package Starter Kit\r\n\r\nThe purpose of this package template starter kit is to provide the data structure and development guidelines for new packages meant for the **Unity Package Manager (UPM)**.\r\n\r\nThis is the first of many steps towards an automated package publishing experience within Unity. This package template starter kit is merely a fraction of the creation, edition, validation, and publishing tools that we will end up with.\r\n\r\nWe hope you enjoy your experience. You can use **#devs-packman** on Slack to provide feedback or ask questions regarding your package development efforts.\r\n\r\n## Are you ready to become a package?\r\nThe Package Manager is a work-in-progress for Unity and, in that sense, there are a few criteria that must be met for your package to be considered on the package list at this time:\r\n- **Your code accesses public Unity C# APIs only.**  If you have a native code component, it will need to ship with an official editor release.  Internal API access might eventually be possible for Unity made packages, but not at this time.\r\n- **Your code doesn't require security, obfuscation, or conditional access control.**  Anyone should be able to download your package and access the source code.\r\n- **You have no urgent need to release your package.**  Our current target for new packages is aligned with 2018.1. Although, based on upcoming package requests and limited packman capacity, that release date is not assured for any package.\r\n- **You are willing to bleed with us a little!** Packman is still in development, and therefore has a few rough edges that will require patience and workarounds.\r\n\r\n## Package structure\r\n\r\n```none\r\n<root>\r\n  ├── package.json\r\n  ├── README.md\r\n  ├── CHANGELOG.md\r\n  ├── LICENSE.md\r\n  ├── QAReport.md\r\n  ├── Editor\r\n  │   ├── Unity.[YourPackageName].Editor.asmdef\r\n  │   └── EditorExample.cs\r\n  ├── Runtime\r\n  │   ├── Unity.[YourPackageName].asmdef\r\n  │   └── RuntimeExample.cs\r\n  ├── Tests\r\n  │   ├── Editor\r\n  │   │   ├── Unity.[YourPackageName].Editor.Tests.asmdef\r\n  │   │   └── EditorExampleTest.cs\r\n  │   └── Runtime\r\n  │       ├── Unity.[YourPackageName].Tests.asmdef\r\n  │       └── RuntimeExampleTest.cs\r\n  ├── Samples\r\n  │   └── SampleExample.cs\r\n  └── Documentation\r\n      ├── your-package-name.md\r\n      └── Images\r\n```\r\n\r\n## Develop your package\r\nPackage development works best within the Unity Editor.  Here's how to set that up:\r\n\r\n1. Fork the `package-template` repository\r\n\r\n    Forking a repository is a simple two-step process.\r\n    - On Gitlab, navigate to the [upm-packages](https://gitlab.internal.unity3d.com/upm-packages), and create a sub-group for feature area.\r\n    - Head over to the [upm-packages/package-template](https://gitlab.internal.unity3d.com/upm-packages/upm-package-template) repository. Click on the **Fork** button at the top-left corner of the page, and follow the instructions to fork the starter kit template into your sub-group.\r\n\r\n    That's it! You now have your own copy (fork) of the original `upm-packages/package-template` repository you can use to develop your package.\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. In a console (or terminal) application, go to the newly created project folder, then clone your newly forked repository into the packages directory.\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n1. Fill in your package information\r\n\r\n\tUpdate the following required fields in file **package.json**:\r\n\t- `\"name\"`: Package name, it should follow this naming convention: `\"com.unity.[your package name]\"`\r\n\t(Example: `\"com.unity.terrain-builder\"`)\r\n\t- `\"displayName\"`: Package user friendly display name. (Example: `\"Terrain Builder SDK\"`). <br>__Note:__ Use a display name that will help users understand what your package is intended for.\r\n\t- `\"version\"`: Package version `\"X.Y.Z\"`, your project **must** adhere to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).\r\n\t\tFollow this guideline:\r\n\t\t- To introduce a new feature or bug fix, increment the minor version (X.**Y**.Z)\r\n\t\t- To introduce a breaking API change, increment the major version (**X**.Y.Z)\r\n\t\t- The patch version (X.Y.**Z**), is reserved for sustainable engineering use only.\r\n\t- `\"unity\"`: Unity Version your package is compatible with. (Example: `\"2018.1\"`)\r\n\t- `\"description\"`: This description appears in the Package Manager window when the user selects this package from the list. For best results, use this text to summarize what the package does and how it can benefit the user.<br>__Note:__ Special formatting characters are supported, including line breaks (`\\n`) and unicode characters such as bullets (`\\u25AA`).<br>For more information, see the [Writing Package docs](https://confluence.hq.unity3d.com/display/DOCS/Writing+Package+docs) page on Confluence.\r\n\r\n\tUpdate the following recommended fields in file **package.json**:\r\n\t- `\"dependencies\"`: List of packages this package depends on.  All dependencies will also be downloaded and loaded in a project with your package.  Here's an example:\r\n        ```\r\n        dependencies: {\r\n          \"com.unity.ads\": \"1.0.0\"\r\n          \"com.unity.analytics\": \"2.0.0\"\r\n        }\r\n        ```\r\n\t- `\"keywords\"`: List of words that will be indexed by the package manager search engine to facilitate discovery.\r\n\t- `\"category\"`: List of Unity defined categories used for browsing and filtering (**In Development**)\r\n\r\n1. Restart Unity. For more information on embedded packages see [here](https://confluence.hq.unity3d.com/display/PAK/How+to+embed+a+package+in+your+project).\r\n\r\n1. Enable package support in the editor (*Internal Feature*).  From the **Project** window's right hang menu, enable `DEVELOPER`->`Show Packages in Project Window` (*only available in developer builds*).  You should now see your package in the Project Window, along with all other available packages for your project.\r\n\r\n1. Update **README.md**\r\n\r\n    The README.md file should contain all pertinent information for developers using your package, such as:\r\n\t* Prerequistes\r\n\t* External tools or development libraries\r\n\t* Required installed Software\r\n\t* Command line examples to build, test, and run your package.\r\n\r\n1. Rename and update **your-package-name.md** documentation file.\r\n\r\n    Use this template to create preliminary, high-level documentation. This document is meant to introduce users to the features and sample files included in your package.\r\n\r\n1. Rename and update assembly definition files.\r\n\r\n\tIf your package requires to isolate Editor code (to make sure it's not included in Runtime build), modify [Editor/Unity.YourPackageName.Editor.asmdef](Editor/Unity.YourPackageName.Editor.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name, suffixed by `.Editor` (i.e `Unity.[YourPackageName].Editor`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t\r\n\tIf your package contains code that needs to be included in Unity runtime builds, modify [Runtime/Unity.YourPackageName.asmdef](Runtime/Unity.YourPackageName.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name (i.e `Unity.[YourPackageName]`)\r\n\t\r\n\tIf your package has Editor code, you **must** have Editor Tests. In that case, modify [Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef](Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Editor.Tests` (i.e `Unity.[YourPackageName].Editor.Tests`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName].Editor` and `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Editor Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\t\r\n\tIf your package has Runtime code, you **must** have Playmode Tests. In that case, modify [Tests/Runtime/Unity.YourPackageName.Tests.asmdef](Tests/Runtime/Unity.YourPackageName.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Tests` (i.e `Unity.[YourPackageName].Tests`) \r\n\t* Assembly **must** reference `Unity.[YourPackageName]`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Playmode Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\r\n>\r\n>  The reason for choosing such name schema is to ensure that the name of the assembly built based on *assembly definition file* (_a.k.a .asmdef_) will follow the .Net [Framework Design Guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/index)\r\n\r\n1. Document your package.\r\n\r\n\t**Document your public APIs**\r\n\t* All public APIs need to be documented with XmlDoc.  If you don't need an API to be accessed by clients, mark it as internal instead.\r\n\t* API documentation is generated from [XmlDoc tags](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/xml-documentation-comments) included with all public APIs found in the package. See [Editor/EditorExample.cs](Editor/EditorExample.cs) for an example.\r\n\t\r\n\t**Document your features**\r\n    * All packages that expose UI in the editor or runtime features should use the documentation template in [Documentation/your-package-name.md](Documentation/your-package-name.md).\r\n\t\r\n\t**Documentation flow**\r\n\t* Documentation needs to be ready when a publish request is sent to Release Management, as they will ask the documentation team to review it.\r\n\t* The package will remain in `preview` mode until the final documentation is completed.  Users will have access to the developer-generated documentation only in preview packages.\r\n\t* When the documentation is completed, the documentation team will update the package git repo with the updates and they will publish it on the web.\r\n\t* The package's development team will then need to submit a new package version with updated docs.\r\n\t* The starting page in the user manual that links to package documentation is [Here](http://docs.hq.unity3d.com/2018.1/Documentation/Manual/PackagesList.html).\r\n\r\n1. Design Guidelines\r\n\r\n * You should follow these design guideline when creating your package\r\n   * [Package design guidelines](https://confluence.hq.unity3d.com/pages/viewpage.action?spaceKey=DEV&title=Package+Design+Guidelines)\r\n   * [Unity design checklist](https://unitytech.github.io/unityeditor-hig/topics/checklist.html)\r\n\r\n2. Add tests to your package.\r\n\r\n\t**Editor tests**\r\n\t* Write all your Editor Tests in `Tests/Editor`\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Editor` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].Editor.Tests\")]`\r\n\r\n\t**Playmode Tests**\r\n\t* Write all your Playmode Tests in `Tests/Runtime`.\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Runtime` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].RuntimeTests\")]`\r\n\r\n3. Update **CHANGELOG.md**\r\n\r\n\tEvery new feature or bug fix should have a trace in this file. For more details on the chosen changelog format, see [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).\r\n\r\n## Create a Pre-Release Package\r\nPre-Release Packages are a great way of getting your features in front of Unity Developers in order to get early feedback on functionality and UI designs.  Pre-Release packages need to go through the publishing to production flow, as would any other package, but with diminished requirements.  Here are the supported Pre-Release tags (to be used in package.json,`version` field), along with the requirements for each one:\r\n\r\n**Experimental**  -  ex: `\"version\" : \"1.2.0-experimental\"`\r\n  * Expected Package structure respected\r\n  * Package loads in Unity Editor without errors\r\n  * License file present\r\n\r\n**Alpha**  -  ex: `\"version\" : \"1.2.0-alpha\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public APIs documented, minimal feature docs exists.\r\n\r\n**Beta** - ex: `\"version\" : \"1.2.0-beta\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public API and Feature Doc are ready for review\r\n  * QAReport filled out with QA details.\r\n\r\n## Register your package\r\n\r\nIf you think you are working on a feature that is a good package candidate, please take a minute to fill-in this form: https://docs.google.com/forms/d/e/1FAIpQLSedxgDcIyf1oPyhWegp5FBvMm63MGAopeJhHDT5bU_BkFPNIQ/viewform?usp=sf_link.\r\n\r\nWorking with the board of dev directors and with product management, we will schedule the entry of the candidates in the ecosystem, based on technical challenges and on our feature roadmap.\r\nDon’t hesitate to reach out and join us on **#devs-packman** on Slack.\r\n\r\n## Share your package\r\n\r\nIf you want to share your project with other developers, the steps are similar to what's presented above. On the other developer's machine:\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. Launch console (or terminal) application, go to the newly created project folder, then clone your repository in the packages directory\r\n\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n\r\n## Dry-Run your package with **UPM**\r\n\r\nBefore publishing your package to production, you must test your package on the Package Manager's **staging** repository.  This is also important as packages are evaluated from staging before being promoted to production.\r\n\r\n1. Publishing your changes to the package manager's **staging** repository.\r\n\r\n\tThe staging repository is monitored by QA and release management, and is where package validation will take place before it is accepted in production. To publish to staging, do the follow:\r\n\t* Join the **#devs-packman** channel on Slack, and request a staging **USERNAME** and **API_KEY**.\r\n\t* [Install NodeJs](https://nodejs.org/en/download/), so you can have access to **npm** (Node Package Manager).\r\n\t* If developing on Windows, [install Curl](https://curl.haxx.se/download.html).  Note: Curl already comes with Mac OS.\r\n\t* Setup your credentials for **npm** by running the following command line from the root folder of your package.\r\n        ```\r\n        curl -u<USERNAME>@unity:<API_KEY> https://staging-packages.unity.com/auth > .npmrc\r\n        ```\r\n\t* You are now ready to publish your package to staging with the following command line, from the root folder of your folder:\r\n      ```\r\n      npm publish\r\n      ```\r\n2. Test your package locally\r\n\r\n    Now that your package is published on the package manager's **staging** repository, you can test your package in the editor by creating a new project, and editing the project's `manifest.json` file to point to your staging package, as such:\r\n      ```\r\n      dependencies: {\r\n        \"com.unity.[your package name]\": \"0.1.0\"\r\n      },\r\n      \"registry\": \"https://staging-packages.unity.com\"\r\n      ```\r\n\r\n## Get your package published to Production\r\n\r\nPackages are promoted to the **production** repository from **staging**, described above. Certain criteria must be met before submitting a request to promote a package to production.\r\n[The list of criteria can be found here](https://docs.google.com/document/d/1TSnlSKJ6_h0C-CYO2LvV0fyGxJvH6OxC2-heyN8o-Gw/edit#heading=h.xxfb5jk2jda2)\r\n\r\nOnce you feel comfortable that your package meets the list of Release Management Criteria, [Submit your package publishing request to Release Management](https://docs.google.com/forms/d/e/1FAIpQLSdSIRO6s6_gM-BxXbDtdzIej-Hhk-3n68xSyC2sM8tp7413mw/viewform).\r\n\r\n**Release management will validate your package content, and check that the editor/playmode tests are passed before promoting the package to production.  You will receive a confirmation email once the package is in production.**\r\n\r\n**You're not done!**\r\nAt this point, your package is available on the cloud, 2 more steps are required to make your package discoverable in the editor:\r\n\r\n1. Contact the Package Manager team in #devs-packman to ask them to add your package to the list of discoverable package for the Unity Editor.  All you need to provide is the package name (com.unity.[your-package-name])\r\n1. If your package is meant to ship with a release of the editor (Unity Recommended Packages), follow these steps:\r\n\t* Modify the editor manifest ``[root]\\External\\PackageManager\\Editor\\Manifest.json`` to include your package in the list of dependencies.\r\n    * Submit one or more Test Project(s) in Ono, so that your new package can be tested in all ABVs moving forward.  The following steps will create a test project that will run in ABVs, load your package into the project, and run all the tests found in your package.  The better your test coverage, the more confident you'll be that your package works with trunk.\r\n    \t* Create a branch in Ono, based on the latest branch this package must be compatible with (trunk, or release branch)\r\n    \t* If your package contains **Editor Tests**:\r\n    \t\t* In ``[root]\\Tests\\Editor.Tests``, create a new EditorTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* A [skeleton of EditorTest Project can be found here](https://oc.unity3d.com/index.php/s/Cldvuy6NpxqYy8y).\r\n    \t\t* Modify the project’s manifest.json file to include the production version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``\r\n    \t* If your package contains **PlaymodeTests**:\r\n    \t\t* In ``[root]\\Tests\\PlaymodeTests``, create a new PlaymodeTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* Modify the project’s manifest.json file to include the staging version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``.\r\n    \t\t* Commit your branch changes to Ono, and run all Windows & Mac Editor/PlayMode tests (not full ABV) in Katana.\r\n    * Once the tests are green on Katana, create your PR, add both `Latest Release Manager` and  `Trunk Merge Queue` as reviewers.\r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_npmUser":{"name":"service-airflow-production@unity","email":"packman-ops+service-airflow-production@unity3d.com"},"_resolved":"","_integrity":"","repository":{"url":"https://github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git","type":"git","revision":"450a35db3030b6a36c7dbbfe94c34575a66024e1","footprint":"222ba8de256cfbcd9749c1b8cb983e8c708eeb7d"},"_npmVersion":"6.13.4","_nodeVersion":"12.14.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.12.0-preview.7","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.1-preview.3","com.unity.burst":"1.2.0-preview.9","com.unity.entities":"0.3.0-preview.4","com.unity.collections":"0.3.0-preview.0","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"9a227596adbaadb61c02cd0f1bd4f69407160475","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.12.0-preview.7.tgz"}},"0.12.0-preview.6":{"_id":"com.unity.dataflowgraph@0.12.0-preview.6","type":"asset","_from":"file:com.unity.dataflowgraph-0.12.0-preview.6.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n\r\n- Start a fresh new Unity project\r\n- Change Player Settings for `Scripting Runtime Version` to `.NET 4.x Equivalent`\r\n- Change Player Settings for `Api Compatiblity Level` to `.NET 4.x`\r\n- Add in the DataFlowGraph package\r\n\r\nYou have __four options__ for that last step:\r\n1. Easy per project package installation\r\n    - Clone this repo to the `Packages/` sub-folder within your Unity project\r\n    - (you don't even need to restart Unity!)\r\n\r\n2. Shared package installation (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine\r\n   - From the PackageManager window, clik the + icon in the bottom of the left column to \"Add package from disk...\"\r\n   - Navigate to the cloned repo and select the package.json file\r\n\r\n3. Shared package installation option 2 (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine (ideally in a folder immediately adjacent to your Unity project folder)\r\n   - Quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"file:../../com.unity.dataflowgraph\"`\r\n\r\n4. Direct link to GitHub repo (does __NOT__ allow for DataFlowGraph framework development)\r\n   - First quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"ssh://git@github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git#master\"`\r\n   - The \"#master\" part can be replaced which any branch name in the DataFlowGraph package repo, or, any specific commit hash.\r\n     Furthermore it can be updated live while Unity is running.\r\n\r\nIn all cases above, if you want to be able to run the DataFlowGraph tests within the TestRunner, also add the following to `manifest.json` after the `dependencies` section:\r\n```\r\n     \"testables\": [\r\n        \"com.unity.dataflowgraph\"\r\n     ]\r\n```\r\n\r\n# Repository CI summary - master\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=master) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=master)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=master) \r\n![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/release-badge.svg) ![ReleaseBadge](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/candidates-badge.svg)\r\n\r\n# Bleeding edge / staging summary\r\n\r\n[![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/build-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependencies-info?branch=staging) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-badge.svg)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/dependants-info) [![](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-badge.svg?branch=staging)](https://badges.cds.internal.unity3d.com/packages/com.unity.dataflowgraph/warnings-info?branch=staging) \r\n\r\n#\r\n\r\n#\r\n\r\n#\r\n\r\n\r\n# UPM Package Starter Kit\r\n\r\nThe purpose of this package template starter kit is to provide the data structure and development guidelines for new packages meant for the **Unity Package Manager (UPM)**.\r\n\r\nThis is the first of many steps towards an automated package publishing experience within Unity. This package template starter kit is merely a fraction of the creation, edition, validation, and publishing tools that we will end up with.\r\n\r\nWe hope you enjoy your experience. You can use **#devs-packman** on Slack to provide feedback or ask questions regarding your package development efforts.\r\n\r\n## Are you ready to become a package?\r\nThe Package Manager is a work-in-progress for Unity and, in that sense, there are a few criteria that must be met for your package to be considered on the package list at this time:\r\n- **Your code accesses public Unity C# APIs only.**  If you have a native code component, it will need to ship with an official editor release.  Internal API access might eventually be possible for Unity made packages, but not at this time.\r\n- **Your code doesn't require security, obfuscation, or conditional access control.**  Anyone should be able to download your package and access the source code.\r\n- **You have no urgent need to release your package.**  Our current target for new packages is aligned with 2018.1. Although, based on upcoming package requests and limited packman capacity, that release date is not assured for any package.\r\n- **You are willing to bleed with us a little!** Packman is still in development, and therefore has a few rough edges that will require patience and workarounds.\r\n\r\n## Package structure\r\n\r\n```none\r\n<root>\r\n  ├── package.json\r\n  ├── README.md\r\n  ├── CHANGELOG.md\r\n  ├── LICENSE.md\r\n  ├── QAReport.md\r\n  ├── Editor\r\n  │   ├── Unity.[YourPackageName].Editor.asmdef\r\n  │   └── EditorExample.cs\r\n  ├── Runtime\r\n  │   ├── Unity.[YourPackageName].asmdef\r\n  │   └── RuntimeExample.cs\r\n  ├── Tests\r\n  │   ├── Editor\r\n  │   │   ├── Unity.[YourPackageName].Editor.Tests.asmdef\r\n  │   │   └── EditorExampleTest.cs\r\n  │   └── Runtime\r\n  │       ├── Unity.[YourPackageName].Tests.asmdef\r\n  │       └── RuntimeExampleTest.cs\r\n  ├── Samples\r\n  │   └── SampleExample.cs\r\n  └── Documentation\r\n      ├── your-package-name.md\r\n      └── Images\r\n```\r\n\r\n## Develop your package\r\nPackage development works best within the Unity Editor.  Here's how to set that up:\r\n\r\n1. Fork the `package-template` repository\r\n\r\n    Forking a repository is a simple two-step process.\r\n    - On Gitlab, navigate to the [upm-packages](https://gitlab.internal.unity3d.com/upm-packages), and create a sub-group for feature area.\r\n    - Head over to the [upm-packages/package-template](https://gitlab.internal.unity3d.com/upm-packages/upm-package-template) repository. Click on the **Fork** button at the top-left corner of the page, and follow the instructions to fork the starter kit template into your sub-group.\r\n\r\n    That's it! You now have your own copy (fork) of the original `upm-packages/package-template` repository you can use to develop your package.\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. In a console (or terminal) application, go to the newly created project folder, then clone your newly forked repository into the packages directory.\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n1. Fill in your package information\r\n\r\n\tUpdate the following required fields in file **package.json**:\r\n\t- `\"name\"`: Package name, it should follow this naming convention: `\"com.unity.[your package name]\"`\r\n\t(Example: `\"com.unity.terrain-builder\"`)\r\n\t- `\"displayName\"`: Package user friendly display name. (Example: `\"Terrain Builder SDK\"`). <br>__Note:__ Use a display name that will help users understand what your package is intended for.\r\n\t- `\"version\"`: Package version `\"X.Y.Z\"`, your project **must** adhere to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).\r\n\t\tFollow this guideline:\r\n\t\t- To introduce a new feature or bug fix, increment the minor version (X.**Y**.Z)\r\n\t\t- To introduce a breaking API change, increment the major version (**X**.Y.Z)\r\n\t\t- The patch version (X.Y.**Z**), is reserved for sustainable engineering use only.\r\n\t- `\"unity\"`: Unity Version your package is compatible with. (Example: `\"2018.1\"`)\r\n\t- `\"description\"`: This description appears in the Package Manager window when the user selects this package from the list. For best results, use this text to summarize what the package does and how it can benefit the user.<br>__Note:__ Special formatting characters are supported, including line breaks (`\\n`) and unicode characters such as bullets (`\\u25AA`).<br>For more information, see the [Writing Package docs](https://confluence.hq.unity3d.com/display/DOCS/Writing+Package+docs) page on Confluence.\r\n\r\n\tUpdate the following recommended fields in file **package.json**:\r\n\t- `\"dependencies\"`: List of packages this package depends on.  All dependencies will also be downloaded and loaded in a project with your package.  Here's an example:\r\n        ```\r\n        dependencies: {\r\n          \"com.unity.ads\": \"1.0.0\"\r\n          \"com.unity.analytics\": \"2.0.0\"\r\n        }\r\n        ```\r\n\t- `\"keywords\"`: List of words that will be indexed by the package manager search engine to facilitate discovery.\r\n\t- `\"category\"`: List of Unity defined categories used for browsing and filtering (**In Development**)\r\n\r\n1. Restart Unity. For more information on embedded packages see [here](https://confluence.hq.unity3d.com/display/PAK/How+to+embed+a+package+in+your+project).\r\n\r\n1. Enable package support in the editor (*Internal Feature*).  From the **Project** window's right hang menu, enable `DEVELOPER`->`Show Packages in Project Window` (*only available in developer builds*).  You should now see your package in the Project Window, along with all other available packages for your project.\r\n\r\n1. Update **README.md**\r\n\r\n    The README.md file should contain all pertinent information for developers using your package, such as:\r\n\t* Prerequistes\r\n\t* External tools or development libraries\r\n\t* Required installed Software\r\n\t* Command line examples to build, test, and run your package.\r\n\r\n1. Rename and update **your-package-name.md** documentation file.\r\n\r\n    Use this template to create preliminary, high-level documentation. This document is meant to introduce users to the features and sample files included in your package.\r\n\r\n1. Rename and update assembly definition files.\r\n\r\n\tIf your package requires to isolate Editor code (to make sure it's not included in Runtime build), modify [Editor/Unity.YourPackageName.Editor.asmdef](Editor/Unity.YourPackageName.Editor.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name, suffixed by `.Editor` (i.e `Unity.[YourPackageName].Editor`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t\r\n\tIf your package contains code that needs to be included in Unity runtime builds, modify [Runtime/Unity.YourPackageName.asmdef](Runtime/Unity.YourPackageName.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name (i.e `Unity.[YourPackageName]`)\r\n\t\r\n\tIf your package has Editor code, you **must** have Editor Tests. In that case, modify [Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef](Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Editor.Tests` (i.e `Unity.[YourPackageName].Editor.Tests`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName].Editor` and `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Editor Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\t\r\n\tIf your package has Runtime code, you **must** have Playmode Tests. In that case, modify [Tests/Runtime/Unity.YourPackageName.Tests.asmdef](Tests/Runtime/Unity.YourPackageName.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Tests` (i.e `Unity.[YourPackageName].Tests`) \r\n\t* Assembly **must** reference `Unity.[YourPackageName]`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Playmode Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\r\n>\r\n>  The reason for choosing such name schema is to ensure that the name of the assembly built based on *assembly definition file* (_a.k.a .asmdef_) will follow the .Net [Framework Design Guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/index)\r\n\r\n1. Document your package.\r\n\r\n\t**Document your public APIs**\r\n\t* All public APIs need to be documented with XmlDoc.  If you don't need an API to be accessed by clients, mark it as internal instead.\r\n\t* API documentation is generated from [XmlDoc tags](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/xml-documentation-comments) included with all public APIs found in the package. See [Editor/EditorExample.cs](Editor/EditorExample.cs) for an example.\r\n\t\r\n\t**Document your features**\r\n    * All packages that expose UI in the editor or runtime features should use the documentation template in [Documentation/your-package-name.md](Documentation/your-package-name.md).\r\n\t\r\n\t**Documentation flow**\r\n\t* Documentation needs to be ready when a publish request is sent to Release Management, as they will ask the documentation team to review it.\r\n\t* The package will remain in `preview` mode until the final documentation is completed.  Users will have access to the developer-generated documentation only in preview packages.\r\n\t* When the documentation is completed, the documentation team will update the package git repo with the updates and they will publish it on the web.\r\n\t* The package's development team will then need to submit a new package version with updated docs.\r\n\t* The starting page in the user manual that links to package documentation is [Here](http://docs.hq.unity3d.com/2018.1/Documentation/Manual/PackagesList.html).\r\n\r\n1. Design Guidelines\r\n\r\n * You should follow these design guideline when creating your package\r\n   * [Package design guidelines](https://confluence.hq.unity3d.com/pages/viewpage.action?spaceKey=DEV&title=Package+Design+Guidelines)\r\n   * [Unity design checklist](https://unitytech.github.io/unityeditor-hig/topics/checklist.html)\r\n\r\n2. Add tests to your package.\r\n\r\n\t**Editor tests**\r\n\t* Write all your Editor Tests in `Tests/Editor`\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Editor` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].Editor.Tests\")]`\r\n\r\n\t**Playmode Tests**\r\n\t* Write all your Playmode Tests in `Tests/Runtime`.\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Runtime` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].RuntimeTests\")]`\r\n\r\n3. Update **CHANGELOG.md**\r\n\r\n\tEvery new feature or bug fix should have a trace in this file. For more details on the chosen changelog format, see [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).\r\n\r\n## Create a Pre-Release Package\r\nPre-Release Packages are a great way of getting your features in front of Unity Developers in order to get early feedback on functionality and UI designs.  Pre-Release packages need to go through the publishing to production flow, as would any other package, but with diminished requirements.  Here are the supported Pre-Release tags (to be used in package.json,`version` field), along with the requirements for each one:\r\n\r\n**Experimental**  -  ex: `\"version\" : \"1.2.0-experimental\"`\r\n  * Expected Package structure respected\r\n  * Package loads in Unity Editor without errors\r\n  * License file present\r\n\r\n**Alpha**  -  ex: `\"version\" : \"1.2.0-alpha\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public APIs documented, minimal feature docs exists.\r\n\r\n**Beta** - ex: `\"version\" : \"1.2.0-beta\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public API and Feature Doc are ready for review\r\n  * QAReport filled out with QA details.\r\n\r\n## Register your package\r\n\r\nIf you think you are working on a feature that is a good package candidate, please take a minute to fill-in this form: https://docs.google.com/forms/d/e/1FAIpQLSedxgDcIyf1oPyhWegp5FBvMm63MGAopeJhHDT5bU_BkFPNIQ/viewform?usp=sf_link.\r\n\r\nWorking with the board of dev directors and with product management, we will schedule the entry of the candidates in the ecosystem, based on technical challenges and on our feature roadmap.\r\nDon’t hesitate to reach out and join us on **#devs-packman** on Slack.\r\n\r\n## Share your package\r\n\r\nIf you want to share your project with other developers, the steps are similar to what's presented above. On the other developer's machine:\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. Launch console (or terminal) application, go to the newly created project folder, then clone your repository in the packages directory\r\n\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n\r\n## Dry-Run your package with **UPM**\r\n\r\nBefore publishing your package to production, you must test your package on the Package Manager's **staging** repository.  This is also important as packages are evaluated from staging before being promoted to production.\r\n\r\n1. Publishing your changes to the package manager's **staging** repository.\r\n\r\n\tThe staging repository is monitored by QA and release management, and is where package validation will take place before it is accepted in production. To publish to staging, do the follow:\r\n\t* Join the **#devs-packman** channel on Slack, and request a staging **USERNAME** and **API_KEY**.\r\n\t* [Install NodeJs](https://nodejs.org/en/download/), so you can have access to **npm** (Node Package Manager).\r\n\t* If developing on Windows, [install Curl](https://curl.haxx.se/download.html).  Note: Curl already comes with Mac OS.\r\n\t* Setup your credentials for **npm** by running the following command line from the root folder of your package.\r\n        ```\r\n        curl -u<USERNAME>@unity:<API_KEY> https://staging-packages.unity.com/auth > .npmrc\r\n        ```\r\n\t* You are now ready to publish your package to staging with the following command line, from the root folder of your folder:\r\n      ```\r\n      npm publish\r\n      ```\r\n2. Test your package locally\r\n\r\n    Now that your package is published on the package manager's **staging** repository, you can test your package in the editor by creating a new project, and editing the project's `manifest.json` file to point to your staging package, as such:\r\n      ```\r\n      dependencies: {\r\n        \"com.unity.[your package name]\": \"0.1.0\"\r\n      },\r\n      \"registry\": \"https://staging-packages.unity.com\"\r\n      ```\r\n\r\n## Get your package published to Production\r\n\r\nPackages are promoted to the **production** repository from **staging**, described above. Certain criteria must be met before submitting a request to promote a package to production.\r\n[The list of criteria can be found here](https://docs.google.com/document/d/1TSnlSKJ6_h0C-CYO2LvV0fyGxJvH6OxC2-heyN8o-Gw/edit#heading=h.xxfb5jk2jda2)\r\n\r\nOnce you feel comfortable that your package meets the list of Release Management Criteria, [Submit your package publishing request to Release Management](https://docs.google.com/forms/d/e/1FAIpQLSdSIRO6s6_gM-BxXbDtdzIej-Hhk-3n68xSyC2sM8tp7413mw/viewform).\r\n\r\n**Release management will validate your package content, and check that the editor/playmode tests are passed before promoting the package to production.  You will receive a confirmation email once the package is in production.**\r\n\r\n**You're not done!**\r\nAt this point, your package is available on the cloud, 2 more steps are required to make your package discoverable in the editor:\r\n\r\n1. Contact the Package Manager team in #devs-packman to ask them to add your package to the list of discoverable package for the Unity Editor.  All you need to provide is the package name (com.unity.[your-package-name])\r\n1. If your package is meant to ship with a release of the editor (Unity Recommended Packages), follow these steps:\r\n\t* Modify the editor manifest ``[root]\\External\\PackageManager\\Editor\\Manifest.json`` to include your package in the list of dependencies.\r\n    * Submit one or more Test Project(s) in Ono, so that your new package can be tested in all ABVs moving forward.  The following steps will create a test project that will run in ABVs, load your package into the project, and run all the tests found in your package.  The better your test coverage, the more confident you'll be that your package works with trunk.\r\n    \t* Create a branch in Ono, based on the latest branch this package must be compatible with (trunk, or release branch)\r\n    \t* If your package contains **Editor Tests**:\r\n    \t\t* In ``[root]\\Tests\\Editor.Tests``, create a new EditorTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* A [skeleton of EditorTest Project can be found here](https://oc.unity3d.com/index.php/s/Cldvuy6NpxqYy8y).\r\n    \t\t* Modify the project’s manifest.json file to include the production version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``\r\n    \t* If your package contains **PlaymodeTests**:\r\n    \t\t* In ``[root]\\Tests\\PlaymodeTests``, create a new PlaymodeTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* Modify the project’s manifest.json file to include the staging version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``.\r\n    \t\t* Commit your branch changes to Ono, and run all Windows & Mac Editor/PlayMode tests (not full ABV) in Katana.\r\n    * Once the tests are green on Katana, create your PR, add both `Latest Release Manager` and  `Trunk Merge Queue` as reviewers.\r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_npmUser":{"name":"service-airflow-production@unity","email":"packman-ops+service-airflow-production@unity3d.com"},"_resolved":"","_integrity":"","repository":{"url":"https://github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git","type":"git","revision":"1e0de74c8f25a23ce039d26b0c2893a873817665"},"_npmVersion":"6.13.4","_nodeVersion":"12.14.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.12.0-preview.6","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.1-preview.3","com.unity.burst":"1.2.0-preview.9","com.unity.entities":"0.3.0-preview.4","com.unity.collections":"0.3.0-preview.0","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"a0ab76d2b4f257a8546ac986366f7d061aa5ebc4","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.12.0-preview.6.tgz"}},"0.11.10-preview":{"_id":"com.unity.dataflowgraph@0.11.10-preview","type":"asset","_from":"file:com.unity.dataflowgraph-0.11.10-preview.tgz","unity":"2019.3","readme":"# Instructions\r\nUsing this package is quite simple:\r\n\r\n- Start a fresh new Unity project\r\n- Change Player Settings for `Scripting Runtime Version` to `.NET 4.x Equivalent`\r\n- Change Player Settings for `Api Compatiblity Level` to `.NET 4.x`\r\n- Add in the DataFlowGraph package\r\n\r\nYou have __four options__ for that last step:\r\n1. Easy per project package installation\r\n    - Clone this repo to the `Packages/` sub-folder within your Unity project\r\n    - (you don't even need to restart Unity!)\r\n\r\n2. Shared package installation (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine\r\n   - From the PackageManager window, clik the + icon in the bottom of the left column to \"Add package from disk...\"\r\n   - Navigate to the cloned repo and select the package.json file\r\n\r\n3. Shared package installation option 2 (allows for development work in the DataFlowGraph framework)\r\n   - Clone this repo to your local machine (ideally in a folder immediately adjacent to your Unity project folder)\r\n   - Quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"file:../../com.unity.dataflowgraph\"`\r\n\r\n4. Direct link to GitHub repo (does __NOT__ allow for DataFlowGraph framework development)\r\n   - First quit Unity\r\n   - Edit your Unity project's `Packages/manifest.json` and add the following to the `dependencies` section:\r\n     `\"com.unity.dataflowgraph\": \"ssh://git@github.cds.internal.unity3d.com/unity/com.unity.dataflowgraph.git#master\"`\r\n   - The \"#master\" part can be replaced which any branch name in the DataFlowGraph package repo, or, any specific commit hash.\r\n     Furthermore it can be updated live while Unity is running.\r\n\r\nIn all cases above, if you want to be able to run the DataFlowGraph tests within the TestRunner, also add the following to `manifest.json` after the `dependencies` section:\r\n```\r\n     \"testables\": [\r\n        \"com.unity.dataflowgraph\"\r\n     ]\r\n```\r\n\r\n#\r\n\r\n#\r\n\r\n#\r\n\r\n#\r\n\r\n\r\n# UPM Package Starter Kit\r\n\r\nThe purpose of this package template starter kit is to provide the data structure and development guidelines for new packages meant for the **Unity Package Manager (UPM)**.\r\n\r\nThis is the first of many steps towards an automated package publishing experience within Unity. This package template starter kit is merely a fraction of the creation, edition, validation, and publishing tools that we will end up with.\r\n\r\nWe hope you enjoy your experience. You can use **#devs-packman** on Slack to provide feedback or ask questions regarding your package development efforts.\r\n\r\n## Are you ready to become a package?\r\nThe Package Manager is a work-in-progress for Unity and, in that sense, there are a few criteria that must be met for your package to be considered on the package list at this time:\r\n- **Your code accesses public Unity C# APIs only.**  If you have a native code component, it will need to ship with an official editor release.  Internal API access might eventually be possible for Unity made packages, but not at this time.\r\n- **Your code doesn't require security, obfuscation, or conditional access control.**  Anyone should be able to download your package and access the source code.\r\n- **You have no urgent need to release your package.**  Our current target for new packages is aligned with 2018.1. Although, based on upcoming package requests and limited packman capacity, that release date is not assured for any package.\r\n- **You are willing to bleed with us a little!** Packman is still in development, and therefore has a few rough edges that will require patience and workarounds.\r\n\r\n## Package structure\r\n\r\n```none\r\n<root>\r\n  ├── package.json\r\n  ├── README.md\r\n  ├── CHANGELOG.md\r\n  ├── LICENSE.md\r\n  ├── QAReport.md\r\n  ├── Editor\r\n  │   ├── Unity.[YourPackageName].Editor.asmdef\r\n  │   └── EditorExample.cs\r\n  ├── Runtime\r\n  │   ├── Unity.[YourPackageName].asmdef\r\n  │   └── RuntimeExample.cs\r\n  ├── Tests\r\n  │   ├── Editor\r\n  │   │   ├── Unity.[YourPackageName].Editor.Tests.asmdef\r\n  │   │   └── EditorExampleTest.cs\r\n  │   └── Runtime\r\n  │       ├── Unity.[YourPackageName].Tests.asmdef\r\n  │       └── RuntimeExampleTest.cs\r\n  ├── Samples\r\n  │   └── SampleExample.cs\r\n  └── Documentation\r\n      ├── your-package-name.md\r\n      └── Images\r\n```\r\n\r\n## Develop your package\r\nPackage development works best within the Unity Editor.  Here's how to set that up:\r\n\r\n1. Fork the `package-template` repository\r\n\r\n    Forking a repository is a simple two-step process.\r\n    - On Gitlab, navigate to the [upm-packages](https://gitlab.internal.unity3d.com/upm-packages), and create a sub-group for feature area.\r\n    - Head over to the [upm-packages/package-template](https://gitlab.internal.unity3d.com/upm-packages/upm-package-template) repository. Click on the **Fork** button at the top-left corner of the page, and follow the instructions to fork the starter kit template into your sub-group.\r\n\r\n    That's it! You now have your own copy (fork) of the original `upm-packages/package-template` repository you can use to develop your package.\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. In a console (or terminal) application, go to the newly created project folder, then clone your newly forked repository into the packages directory.\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n1. Fill in your package information\r\n\r\n\tUpdate the following required fields in file **package.json**:\r\n\t- `\"name\"`: Package name, it should follow this naming convention: `\"com.unity.[your package name]\"`\r\n\t(Example: `\"com.unity.terrain-builder\"`)\r\n\t- `\"displayName\"`: Package user friendly display name. (Example: `\"Terrain Builder SDK\"`). <br>__Note:__ Use a display name that will help users understand what your package is intended for.\r\n\t- `\"version\"`: Package version `\"X.Y.Z\"`, your project **must** adhere to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).\r\n\t\tFollow this guideline:\r\n\t\t- To introduce a new feature or bug fix, increment the minor version (X.**Y**.Z)\r\n\t\t- To introduce a breaking API change, increment the major version (**X**.Y.Z)\r\n\t\t- The patch version (X.Y.**Z**), is reserved for sustainable engineering use only.\r\n\t- `\"unity\"`: Unity Version your package is compatible with. (Example: `\"2018.1\"`)\r\n\t- `\"description\"`: This description appears in the Package Manager window when the user selects this package from the list. For best results, use this text to summarize what the package does and how it can benefit the user.<br>__Note:__ Special formatting characters are supported, including line breaks (`\\n`) and unicode characters such as bullets (`\\u25AA`).<br>For more information, see the [Writing Package docs](https://confluence.hq.unity3d.com/display/DOCS/Writing+Package+docs) page on Confluence.\r\n\r\n\tUpdate the following recommended fields in file **package.json**:\r\n\t- `\"dependencies\"`: List of packages this package depends on.  All dependencies will also be downloaded and loaded in a project with your package.  Here's an example:\r\n        ```\r\n        dependencies: {\r\n          \"com.unity.ads\": \"1.0.0\"\r\n          \"com.unity.analytics\": \"2.0.0\"\r\n        }\r\n        ```\r\n\t- `\"keywords\"`: List of words that will be indexed by the package manager search engine to facilitate discovery.\r\n\t- `\"category\"`: List of Unity defined categories used for browsing and filtering (**In Development**)\r\n\r\n1. Restart Unity. For more information on embedded packages see [here](https://confluence.hq.unity3d.com/display/PAK/How+to+embed+a+package+in+your+project).\r\n\r\n1. Enable package support in the editor (*Internal Feature*).  From the **Project** window's right hang menu, enable `DEVELOPER`->`Show Packages in Project Window` (*only available in developer builds*).  You should now see your package in the Project Window, along with all other available packages for your project.\r\n\r\n1. Update **README.md**\r\n\r\n    The README.md file should contain all pertinent information for developers using your package, such as:\r\n\t* Prerequistes\r\n\t* External tools or development libraries\r\n\t* Required installed Software\r\n\t* Command line examples to build, test, and run your package.\r\n\r\n1. Rename and update **your-package-name.md** documentation file.\r\n\r\n    Use this template to create preliminary, high-level documentation. This document is meant to introduce users to the features and sample files included in your package.\r\n\r\n1. Rename and update assembly definition files.\r\n\r\n\tIf your package requires to isolate Editor code (to make sure it's not included in Runtime build), modify [Editor/Unity.YourPackageName.Editor.asmdef](Editor/Unity.YourPackageName.Editor.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name, suffixed by `.Editor` (i.e `Unity.[YourPackageName].Editor`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t\r\n\tIf your package contains code that needs to be included in Unity runtime builds, modify [Runtime/Unity.YourPackageName.asmdef](Runtime/Unity.YourPackageName.asmdef). Otherwise, delete the file.\r\n\t* Name **must** match your package name (i.e `Unity.[YourPackageName]`)\r\n\t\r\n\tIf your package has Editor code, you **must** have Editor Tests. In that case, modify [Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef](Tests/Editor/Unity.YourPackageName.Editor.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Editor.Tests` (i.e `Unity.[YourPackageName].Editor.Tests`)\r\n\t* Assembly **must** reference `Unity.[YourPackageName].Editor` and `Unity.[YourPackageName]` (if you have any Runtime)\r\n\t* Platforms **must** include `\"Editor\"`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Editor Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\t\r\n\tIf your package has Runtime code, you **must** have Playmode Tests. In that case, modify [Tests/Runtime/Unity.YourPackageName.Tests.asmdef](Tests/Runtime/Unity.YourPackageName.Tests.asmdef).\r\n\t* Name **must** match your package name, suffixed by `.Tests` (i.e `Unity.[YourPackageName].Tests`) \r\n\t* Assembly **must** reference `Unity.[YourPackageName]`\r\n\t* Optional Unity references **must** include `\"TestAssemblies\"` to allow your Playmode Tests to show up in the Test Runner/run on Katana when your package is listed in project manifest `testables`\r\n\r\n>\r\n>  The reason for choosing such name schema is to ensure that the name of the assembly built based on *assembly definition file* (_a.k.a .asmdef_) will follow the .Net [Framework Design Guidelines](https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/index)\r\n\r\n1. Document your package.\r\n\r\n\t**Document your public APIs**\r\n\t* All public APIs need to be documented with XmlDoc.  If you don't need an API to be accessed by clients, mark it as internal instead.\r\n\t* API documentation is generated from [XmlDoc tags](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/xml-documentation-comments) included with all public APIs found in the package. See [Editor/EditorExample.cs](Editor/EditorExample.cs) for an example.\r\n\t\r\n\t**Document your features**\r\n    * All packages that expose UI in the editor or runtime features should use the documentation template in [Documentation/your-package-name.md](Documentation/your-package-name.md).\r\n\t\r\n\t**Documentation flow**\r\n\t* Documentation needs to be ready when a publish request is sent to Release Management, as they will ask the documentation team to review it.\r\n\t* The package will remain in `preview` mode until the final documentation is completed.  Users will have access to the developer-generated documentation only in preview packages.\r\n\t* When the documentation is completed, the documentation team will update the package git repo with the updates and they will publish it on the web.\r\n\t* The package's development team will then need to submit a new package version with updated docs.\r\n\t* The starting page in the user manual that links to package documentation is [Here](http://docs.hq.unity3d.com/2018.1/Documentation/Manual/PackagesList.html).\r\n\r\n1. Design Guidelines\r\n\r\n * You should follow these design guideline when creating your package\r\n   * [Package design guidelines](https://confluence.hq.unity3d.com/pages/viewpage.action?spaceKey=DEV&title=Package+Design+Guidelines)\r\n   * [Unity design checklist](https://unitytech.github.io/unityeditor-hig/topics/checklist.html)\r\n\r\n2. Add tests to your package.\r\n\r\n\t**Editor tests**\r\n\t* Write all your Editor Tests in `Tests/Editor`\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Editor` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].Editor.Tests\")]`\r\n\r\n\t**Playmode Tests**\r\n\t* Write all your Playmode Tests in `Tests/Runtime`.\r\n\t* If your tests require access to internal methods, add an `AssemblyInfo.cs` file to your `Runtime` code and use `[assembly: InternalsVisibleTo(\"Unity.[YourPackageName].RuntimeTests\")]`\r\n\r\n3. Update **CHANGELOG.md**\r\n\r\n\tEvery new feature or bug fix should have a trace in this file. For more details on the chosen changelog format, see [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).\r\n\r\n## Create a Pre-Release Package\r\nPre-Release Packages are a great way of getting your features in front of Unity Developers in order to get early feedback on functionality and UI designs.  Pre-Release packages need to go through the publishing to production flow, as would any other package, but with diminished requirements.  Here are the supported Pre-Release tags (to be used in package.json,`version` field), along with the requirements for each one:\r\n\r\n**Experimental**  -  ex: `\"version\" : \"1.2.0-experimental\"`\r\n  * Expected Package structure respected\r\n  * Package loads in Unity Editor without errors\r\n  * License file present\r\n\r\n**Alpha**  -  ex: `\"version\" : \"1.2.0-alpha\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public APIs documented, minimal feature docs exists.\r\n\r\n**Beta** - ex: `\"version\" : \"1.2.0-beta\"`\r\n  * Feature is in the product roadmap.\r\n  * Test coverage is good.\r\n  * Public API and Feature Doc are ready for review\r\n  * QAReport filled out with QA details.\r\n\r\n## Register your package\r\n\r\nIf you think you are working on a feature that is a good package candidate, please take a minute to fill-in this form: https://docs.google.com/forms/d/e/1FAIpQLSedxgDcIyf1oPyhWegp5FBvMm63MGAopeJhHDT5bU_BkFPNIQ/viewform?usp=sf_link.\r\n\r\nWorking with the board of dev directors and with product management, we will schedule the entry of the candidates in the ecosystem, based on technical challenges and on our feature roadmap.\r\nDon’t hesitate to reach out and join us on **#devs-packman** on Slack.\r\n\r\n## Share your package\r\n\r\nIf you want to share your project with other developers, the steps are similar to what's presented above. On the other developer's machine:\r\n\r\n1. Start **Unity**, create a local empty project.\r\n\r\n1. Launch console (or terminal) application, go to the newly created project folder, then clone your repository in the packages directory\r\n\r\n    ```none\r\n    cd <YourProjectPath>/UnityPackageManager\r\n    git clone https://gitlab.internal.unity3d.com/upm-packages/[your sub-group]/[your package name].git com.unity.[your package name]\r\n    ```\r\n    __Note:__ Your directory name must be the name of your package (Example: `\"com.unity.terrain-builder\"`)\r\n\r\n## Dry-Run your package with **UPM**\r\n\r\nBefore publishing your package to production, you must test your package on the Package Manager's **staging** repository.  This is also important as packages are evaluated from staging before being promoted to production.\r\n\r\n1. Publishing your changes to the package manager's **staging** repository.\r\n\r\n\tThe staging repository is monitored by QA and release management, and is where package validation will take place before it is accepted in production. To publish to staging, do the follow:\r\n\t* Join the **#devs-packman** channel on Slack, and request a staging **USERNAME** and **API_KEY**.\r\n\t* [Install NodeJs](https://nodejs.org/en/download/), so you can have access to **npm** (Node Package Manager).\r\n\t* If developing on Windows, [install Curl](https://curl.haxx.se/download.html).  Note: Curl already comes with Mac OS.\r\n\t* Setup your credentials for **npm** by running the following command line from the root folder of your package.\r\n        ```\r\n        curl -u<USERNAME>@unity:<API_KEY> https://staging-packages.unity.com/auth > .npmrc\r\n        ```\r\n\t* You are now ready to publish your package to staging with the following command line, from the root folder of your folder:\r\n      ```\r\n      npm publish\r\n      ```\r\n2. Test your package locally\r\n\r\n    Now that your package is published on the package manager's **staging** repository, you can test your package in the editor by creating a new project, and editing the project's `manifest.json` file to point to your staging package, as such:\r\n      ```\r\n      dependencies: {\r\n        \"com.unity.[your package name]\": \"0.1.0\"\r\n      },\r\n      \"registry\": \"https://staging-packages.unity.com\"\r\n      ```\r\n\r\n## Get your package published to Production\r\n\r\nPackages are promoted to the **production** repository from **staging**, described above. Certain criteria must be met before submitting a request to promote a package to production.\r\n[The list of criteria can be found here](https://docs.google.com/document/d/1TSnlSKJ6_h0C-CYO2LvV0fyGxJvH6OxC2-heyN8o-Gw/edit#heading=h.xxfb5jk2jda2)\r\n\r\nOnce you feel comfortable that your package meets the list of Release Management Criteria, [Submit your package publishing request to Release Management](https://docs.google.com/forms/d/e/1FAIpQLSdSIRO6s6_gM-BxXbDtdzIej-Hhk-3n68xSyC2sM8tp7413mw/viewform).\r\n\r\n**Release management will validate your package content, and check that the editor/playmode tests are passed before promoting the package to production.  You will receive a confirmation email once the package is in production.**\r\n\r\n**You're not done!**\r\nAt this point, your package is available on the cloud, 2 more steps are required to make your package discoverable in the editor:\r\n\r\n1. Contact the Package Manager team in #devs-packman to ask them to add your package to the list of discoverable package for the Unity Editor.  All you need to provide is the package name (com.unity.[your-package-name])\r\n1. If your package is meant to ship with a release of the editor (Unity Recommended Packages), follow these steps:\r\n\t* Modify the editor manifest ``[root]\\External\\PackageManager\\Editor\\Manifest.json`` to include your package in the list of dependencies.\r\n    * Submit one or more Test Project(s) in Ono, so that your new package can be tested in all ABVs moving forward.  The following steps will create a test project that will run in ABVs, load your package into the project, and run all the tests found in your package.  The better your test coverage, the more confident you'll be that your package works with trunk.\r\n    \t* Create a branch in Ono, based on the latest branch this package must be compatible with (trunk, or release branch)\r\n    \t* If your package contains **Editor Tests**:\r\n    \t\t* In ``[root]\\Tests\\Editor.Tests``, create a new EditorTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* A [skeleton of EditorTest Project can be found here](https://oc.unity3d.com/index.php/s/Cldvuy6NpxqYy8y).\r\n    \t\t* Modify the project’s manifest.json file to include the production version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``\r\n    \t* If your package contains **PlaymodeTests**:\r\n    \t\t* In ``[root]\\Tests\\PlaymodeTests``, create a new PlaymodeTest Project (for new packages use **YourPackageName**) or use an existing project (for new versions of existing package).\r\n    \t\t* Modify the project’s manifest.json file to include the staging version of the package (name@version).\r\n    \t\t* Your project's manifest.json file should contain the following line: ``\"testables\" : [ \"com.unity.[your package name]\" ]``.\r\n    \t\t* Commit your branch changes to Ono, and run all Windows & Mac Editor/PlayMode tests (not full ABV) in Katana.\r\n    * Once the tests are green on Katana, create your PR, add both `Latest Release Manager` and  `Trunk Merge Queue` as reviewers.\r\n","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"_npmUser":{"name":"service-airflow-production@unity","email":"packman-ops+service-airflow-production@unity3d.com"},"_resolved":"","_integrity":"","repository":{"url":"git@github.cds.internal.unity3d.com:unity/com.unity.dataflowgraph.git","type":"git","revision":"5a64b411e7e4ba5e6dd521a05ca9e6fe81dc1441"},"_npmVersion":"6.12.1","_nodeVersion":"12.13.1","readmeFilename":"README.md","name":"com.unity.dataflowgraph","version":"0.11.10-preview","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.2.1-preview.3","com.unity.burst":"1.2.0-preview.9","com.unity.entities":"0.3.0-preview.4","com.unity.collections":"0.3.0-preview.0","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"c011c5b8e77ebab3f29db6d1953774b22ffd43fa","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.11.10-preview.tgz"}},"0.11.9-preview":{"_id":"com.unity.dataflowgraph@0.11.9-preview","type":"asset","unity":"2019.3","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"scripts":{},"repository":{"url":"git@github.cds.internal.unity3d.com:unity/com.unity.dataflowgraph.git","type":"git","revision":"cd406036657764efa2fdd1d12cbd6f65424ca85f"},"name":"com.unity.dataflowgraph","version":"0.11.9-preview","displayName":"Data Flow Graph","description":"Data Flow Graph delivers DOTS-optimized code for graph-like problems, i.e., where order-of-execution is important.\n\nThis is a highly experimental package and should NOT be considered suitable for production situations.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.1.0-preview","com.unity.burst":"1.1.2","com.unity.entities":"0.1.0-preview","com.unity.collections":"0.1.0-preview","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"ae9b28f81f90eb0a58cd6ed8b0bf33433f6493b7","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.11.9-preview.tgz"}},"0.11.8-preview":{"_id":"com.unity.dataflowgraph@0.11.8-preview","type":"asset","unity":"2019.3","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"scripts":{},"repository":{"url":"git@github.cds.internal.unity3d.com:unity/com.unity.dataflowgraph.git","type":"git","revision":"6533886de559b1ad77a3981b0dcf4cc2108521ea"},"name":"com.unity.dataflowgraph","version":"0.11.8-preview","displayName":"Data Flow Graph","description":"This package contains a framework for authoring composable nodes that form a processing graph.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.1.0-preview","com.unity.burst":"1.1.2","com.unity.entities":"0.1.0-preview","com.unity.collections":"0.1.0-preview","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"f39dd865375e29ac7c5fc4ef4841bb9c9a6a946d","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.11.8-preview.tgz"}},"0.11.7-preview":{"_id":"com.unity.dataflowgraph@0.11.7-preview","type":"asset","unity":"2019.3","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"scripts":{},"repository":{"url":"git@github.cds.internal.unity3d.com:unity/com.unity.dataflowgraph.git","type":"git","revision":"74b90936d9d2f2e0f731a6a6e9b846ec7ea17b66"},"name":"com.unity.dataflowgraph","version":"0.11.7-preview","displayName":"Data Flow Graph","description":"This package contains a framework for authoring composable nodes that form a processing graph.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.1.0-preview","com.unity.burst":"1.1.2","com.unity.entities":"0.1.0-preview","com.unity.collections":"0.1.0-preview","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"c78ae99ad447cf7ea474a19d100cce8e4d98a2c7","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.11.7-preview.tgz"}},"0.11.6-preview":{"_id":"com.unity.dataflowgraph@0.11.6-preview","type":"asset","unity":"2019.3","samples":[{"path":"Samples~/Example","description":"Very basic framework usage/authoring example.","displayName":"Examples"},{"path":"Samples~/Tour","description":"A guided tour of the API via commented and runnable code examples.","displayName":"Guided Tour in Code"}],"scripts":{},"repository":{"url":"git@github.cds.internal.unity3d.com:unity/com.unity.dataflowgraph.git","type":"git","revision":"8a0bb129b9bd97b11c581149715ebb5a0311c1c1"},"name":"com.unity.dataflowgraph","version":"0.11.6-preview","displayName":"Data Flow Graph","description":"This package contains a framework for authoring composable nodes that form a processing graph.","keywords":["graph","processing"],"dependencies":{"com.unity.jobs":"0.1.0-preview","com.unity.burst":"1.1.2","com.unity.entities":"0.1.0-preview","com.unity.collections":"0.1.0-preview","com.unity.mathematics":"1.1.0"},"dist":{"shasum":"072b7c02b5bed42fab2e3fcb25a49d0f36f54f80","tarball":"https://download.packages.unity.com/com.unity.dataflowgraph/-/com.unity.dataflowgraph-0.11.6-preview.tgz"}}},"time":{"0.19.0-preview.7":"2021-01-22T16:58:54.000Z","0.18.0-preview.3":"2020-10-29T22:44:09.000Z","0.17.0-preview.4":"2020-09-15T00:22:42.000Z","0.16.0-preview.3":"2020-08-20T18:26:37.000Z","0.16.0-preview.2":"2020-07-31T22:33:38.000Z","0.15.0-preview.5":"2020-06-18T11:11:56.000Z","0.15.0-preview.4":"2020-06-16T11:49:49.000Z","0.14.0-preview.2":"2020-05-07T20:48:25.000Z","0.14.0-preview.1":"2020-04-22T13:32:56.000Z","0.13.0-preview.3":"2020-04-14T16:15:41.000Z","0.13.0-preview.2":"2020-03-27T20:12:57.000Z","0.12.0-preview.7":"2020-03-11T20:50:43.000Z","0.12.0-preview.6":"2020-02-07T18:38:54.000Z","0.11.10-preview":"2019-12-06T15:31:30.000Z","0.11.9-preview":"2019-11-13T17:02:02.000Z","0.11.8-preview":"2019-10-23T21:01:42.000Z","0.11.7-preview":"2019-10-16T20:01:38.000Z","0.11.6-preview":"2019-10-07T18:01:43.000Z"},"dist-tags":{"latest":"0.19.0-preview.7"},"etag":"\"20b9a-PMCkO1G7x6L1j2TLKFE12KNVEuU\""}