The plugins and themes in /dist/ are built from their respective trunks. With 0.7 potentially being a big release for themers, I assume there will be some new functionality there soon that would make the zips unusable for people not keeping current with HEAD.
This isn't the first time this situation has come up - this happened prior to the 0.6 release as well, particularly with the plugins. We've got /branches and /tags in all of the plugin and theme directories, but their use is neither consistent nor frequent. In discussions with ringmaster it has been suggested that we stop zipping up trunk -- and could even abolish it altogether -- and use tags and branches instead to make zips of releases and development. For example, the twitter plugin: Branches for 0.6 and 0.7 would be created. For 0.6.x it is currently stable at version 0.12, so a tag would be created, something like 0.6-0.12, and that could be zipped up as the 0.6 stable release. If more 0.6-compatible features are added to it, they'd appear in the 0.6 development branch until tagged (as 0.6-13, perhaps). For 0.7 the new cache $keep should be used, so that would go in the 0.7 branch, and more development could continue without affecting 0.6.x users. Plugins and themes that are not fully tested with, say, the current release version would not be tagged until they are fixed (such as photoblog). Those ones would only have a development version, and wherever these are displayed (plugin directory to the rescue) would need to indicate as such. Such a system might sound complex, and will add a little complexity for checking out and downloading the plugins, but some new best practices should alleviate the former, and a plugin directory (which is still being worked on) would make downloading the proper versions easier and more reliable for users of all versions. I'm willing to help with the moves (creating branches and deleting trunks), but I'm sure there are details I've missed, or better suggestions, before I start making major changes like this to the repository. Any thoughts? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
