For a Piwik PRO developer always specify a max version for a plugin by default #9511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refs #8695
This is to be defined whether it's actually needed / wanted by Piwik PRO developers.
Piwik PRO developers would enable Piwik PRO mode initially with
./console development:enable --piwikpro
Following
development:enable
commands would not need this flag as we wouldn't change it afterwards anymore. It would be otherwise forgotton and annoying to always having to add this flag.When this mode is enabled, and a plugin is generated, we automatically specify a maximum supported Piwik version in
plugin.json
. Instead ofwe specify
for Piwik PRO developers. From my understanding in #8695 this is what Piwik PRO developers want. So far it was specified in
.travis.yml
. Please note that when a max version is specified, it cannot be installed on a later Piwik version. This is something that needs to be configured.Also see related PR matomo-org/travis-scripts#21