Switch plugin release back to 11.1-RELEASE in 11.1-RELEASE branch of freenas/iocage-ix-plugins
Given the issues/developments referenced below, does it make sense to flip the "release" field in the manifest.json files of the 11.1-RELEASE branch of the plugin repository https://github.com/freenas/iocage-ix-plugins from 11.2-RELEASE back to 11.1-RELEASE?
If not, the iocage plugin infrastructure will be/stay broken for people on the FreeNAS-11-STABLE train.
#1 Updated by Dru Lavigne about 2 years ago
- Tracker changed from Idea to Feature
- Status changed from New Idea to Closed
- Target version set to N/A
- Idea Status deleted (
- Severity set to New
- Reason for Closing set to Third Party to Resolve
- Needs QA set to Yes
- Needs Doc set to Yes
- Needs Merging set to Yes
- Needs Automation set to No
- Support Suite Ticket set to n/a
Thank you for the idea Jurgen. Going forward it won't be an issue as we will be branching that repo for each release/update beginning with BETA3. For those users who used iocage from the CLI as an experimental feature on 11.1, we encourage them to recreate their plugins on the 11.2 series.