Hi, @ryanchristo. I would appreciate an update on your recommended strategy for stress free active development with colony.
I am running into issues like this one that are affecting my development: https://github.com/JoinColony/colonyJS/issues/338
I just spent an hour trying to figure out why my token symbol and name were not getting set and then came across this.
This is only on the development branch, but is really a hotfix because it is a bug in the current colonyStarter, etc.
You recommended I keep my colony packages up to date, but I am not sure if that includes beta releases. My uncertainty is compounded by the fact that you commented that I am not supposed to update ethers to the latest version, as that breaks the colony ethers adapter.
I know that the state of colonyJS and the colonyNetwork are closely linked, so I am also careful for that reason.
Can you recommend if I should upgrade to the beta versions of colonyJS as they come out? Will they break with the current colonyNetwork available in the latest colony cli beta version?
When is the release of the new major version planned that you have mentioned and how will that affect this situation?
I am excited about Colony, but the level of “bleeding edge” I am running into is frustrating. I know your team is working hard, but I hope to find a way where I can development for 6 months on a particular set of versions and then upgrade smoothly to the latest version following the notes on breaking changes provided in the release notes. Or if there were an upgrade tool available to migrate between versions that addressed breaking changes that would be even better.