-
Notifications
You must be signed in to change notification settings - Fork 413
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a4d023e
commit 14466ae
Showing
1 changed file
with
2 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14466ae
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Yahnis,
thanks for the update. just one question: if you update version to v1.6.1, dont you also need to update all occurences of PluginUpdateChecker_1_6 to PluginUpdateChecker_1_6_1?
best,
Robert
14466ae
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no API changes, so I don't think that's necessary. The class names have version suffixes to allow plugins to request a specific version of the library when multiple versions are loaded at the same time (e.g. by two different plugins). In this case, there's no need for that since 1.6 and 1.6.1 releases are functionally almost identical and differ only in terms of licensing.
14466ae
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, thanks for clarification!
14466ae
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only major difference is the frequency it will check for updates based on an updated set of filters in WP