Support dedicated package versions per context
It should be possible to run different versions of a package depending on the application context. This would allow anyone to test new versions in dev context before staging it to production.
As already discussed, the directory structure should be:
It should still be possible to have only one version for all contexts:
If there are context specific versions or not can be detected by checking for the existence of the Meta/Package.xml
Updated by Christopher Hlubek over 11 years ago
- Status changed from New to Accepted
I think the latest consensus was to allow multiple package versions inside each package directory and specify the activated version in the specific (per context) PackageStates.yml, e.g.:
Blog: state: active version: 0.2.2
An explicit version number would allow for a seamless upgrade of packages, since the old package will run as is until the new package is fully installed and activated in PackageStates.yml.
Updated by Karsten Dambekalns over 8 years ago
- Status changed from Accepted to Rejected
- Assignee changed from Christopher Hlubek to Karsten Dambekalns
- Has patch set to No
This would clash with the way composer manages packages. And in the last years, noone really needed it, or it would have been implemented. ;)