> Whether a plugin is compatible with the environment it runs in is not a > facet of the version of the plugin. A plugin that uses a single, simple > hook that operates the same way through 4 core versions of Habari should > not need to update its compatibility requirements to keep up with those > Habari releases.
Agreed. > Likewise, a theme that requires a tag cloud should not look for a plugin > named "RNTagCloud" nor should it look for a specific version of a > specifically-named plugin. Agreed there, too. > Instead, we keep a catalog of feature tags to use in the "requires", > "conflicts", "recommends", and "provides" sections of the plugin info > xml. The core system reports on compatibility between previously > installed items and new items. The example in the wiki (http://wiki.habariproject.org/en/pluggable#provides) is: <provides> <feature url="http://wiki.habariproject.org/en/feature/podcast";>podcast</feature> </provides> Does this mean that the "podcast" hooks can never change? What if we have "podcast2"? I guess I just don't understand. > None of that works really well with simple version number checking, and > I believe it's one of the major complaints people have about OBT that I > would personally love to address. Even doing it this way, API > compatibility makes sense to do (since that's how we're delineating core > major versions) by using a "core-1.x" (literally "x") feature tag. > > To wrap back around to version numbers: Version numbers are a useful > primary indicator for what version of a plugin is the latest and should > be compatible with the version of Habari that is installed, but they > should not be the ultimate indicator of compatibility. I buy this. (-: If we have another way to provide compatibility (and it looks like we do, I'd just never noticed.. my fault), then version numbering isn't a good way to check this. I am, still, however, against bucking conventional wisdom and dropping versions from trunk altogether. > Sorting out > whether a plugin is an in-development version of a > specifically-versioned plugin seems the only real concern, since it > would otherwise be difficult to tell. You seem to agree. What's your opinion on how to do this? S -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
