Despite everyone’s best efforts, we will find bugs in our hApps, add important features, etc. How to we manage these changes from the perspective of the users, developers, and administrators?
I’m just highlighting that this an open question for most of us out there as evidenced by things like this empty link: Guidebook: Creating Versioned Releases. I know there is some kind of work that is going to go into this so the question is more what kind of ecosystem expectations do we have. I could imagine that there is a lot of churn, dead-ends, and consolidation that can happen as a lot of h-apps are developed and the space settles down. This would mean that from the start we would need to be thinking a lot about the stuff that I think Learn more about Ceptr had some really good ideas on - how to design in a way that gives users a lot of flexibility, keeps data from getting stranded in old chains, and lets things improve regularly. Do I have to assume every upgrade is a minority fork until I get the majority to switch? New versions could be designed with migrate functions that let users opt to pull in all their old data or maybe there is some other approach in the works to solve this problem.