I went ahead and updated us to the new version of Zos (renamed OpenZeppelinSDK)
I figured we might as well do it now before we're live.
Things are slightly different now:
zos commands become openzeppelin or oz
config files are now in the .openzeppelin directory, and are renamed slightly.
Remove DAOStack integration tests
I wrote these tests into an Arc fork - they require a different environment in terms of compiler & dependencies (openzeppelin-solidity vs openzeppelin-eth).
I think they'd be best in their own package anyways, as opposed to in the core BC-DAO repo. (The same would be true if we did integrations with another DAO platform)
Zos -> OZ
I went ahead and updated us to the new version of Zos (renamed OpenZeppelinSDK) I figured we might as well do it now before we're live.
Things are slightly different now: zos commands become openzeppelin or oz config files are now in the .openzeppelin directory, and are renamed slightly.
Remove DAOStack integration tests
I wrote these tests into an Arc fork - they require a different environment in terms of compiler & dependencies (openzeppelin-solidity vs openzeppelin-eth).
I think they'd be best in their own package anyways, as opposed to in the core BC-DAO repo. (The same would be true if we did integrations with another DAO platform)