zfcampus/zf-apigility-skeleton

Question: what's the recommended approach / best practice to upgrade the base skeleton with existing API?

liuwenchao opened this issue · 1 comments

what's the recommended approach / best practice to upgrade the base skeleton with existing API?

I worry about the complexity of future upgrading, any suggestion? Thanks!

The skeleton should rarely, if ever, change going forward. What will change are the modules it incorporates -- and these are all pulled in as dependencies via Composer. What this means is that, realistically, you should be able to run a composer update or php composer.phar update within your project to pull in the latest code at any time.

If/when there are changes to the skeleton that are not provided by dependencies, we will message those changes in release announcements. In most situations, these should only be around exposing new features and/or modifying how features are configured.