Move to upm #1
Description
With the release of 2019.3, upm brings integrated git package support. This makes using packages, at least outside the asset store simple.
pros
- Installing is easier, no need to download / track the .unitypackage file
- Updating can be handled by the Unity editor's integrated upm tools
- Testing is integrated into upm packages
cons
- Before 2019.3, installing via upm requires an add-on for GUI or manual manifest editing
- upm packages can't be loaded into Unity by themselves, they require a project (the repo would not contain everything needed to work on Replicator)
- .asmdef structure is required, meaning Replicator will make projects which use it depend on that system
For me, one of the biggest blockers is the .asmdef use. In some projects, it's not necessarily beneficial to have many modules in that architecture. With the integration of git upm packages in Unity 2019.3, it makes sense as a distribution mode, especially given that updating may be handled by that system, and git url's allow for very configurable version targeting.
All in, I think the best move is to retain the repository as a full project, and use a script to push to a upm-specific branch. This could also mean the possibility of retaining .unitypackage releases (for now, at least).