What actually happened with the "migrations"-folder?

[abcoathup]

Hi @sbrichards welcome to the community.

I have created an issue: https://github.com/zeppelinos/zepkit/issues/29 for your suggestion to add to the README.

My understanding of the migrations folder is for when a user wants to use truffle migrations as well as ZeppelinOS. This could be where a user has a mixed project of upgradeable contracts deployed using ZeppelinOS and non-upgradeable contracts deployed using Truffle migrations.

There was a discussion recently on how to manage non-upgradeable projects in ZeppelinOS:

How would you manage non-upgradeable contracts on ZeppelinOS?

An issue we have been long discussing is how ZeppelinOS should handle non-upgradeable deployments. Whenever you deploy a contract using zos create a new upgradeable proxy is created behind the scenes. If you want to make a contract non-upgradeable, your only options are to set the upgradeability admin of the contract to the null address (so no one can actually upgrade it), or use another tool altogether. None of these options are good. We have identified three different options to implement thi…

Also information about minimal proxies support in ZeppelinOS in the May development update:

ZeppelinOS May 2019 development update

Hey folks! After the release of ZeppelinOS 2.3.0 last week, we wanted to share with you what has kept us busy during May. Though most efforts went towards stabilizing 2.3, we also have some interesting features coming up for the next version, such as new proxy patterns and new commands for managing funds and transactions directly from the command line. We are also exploring the current state of front-end libraries for developing DApps, so you may expect a surprise from us on that front in the up…