One quick question: do we really need to have the Habari version in the tag? This will unnecessarily result in many duplicates of the same plugin with the only difference being the tag. This will also potentially lead to an administrative nightmare and confusion with users.
I know why there is the desire for this, but maybe we should make this an exception rather than the norm. Or maybe extend plugins to include a "compatible" or "min/max version" option in the xml file? You're already parsing the file, so one or two more fields to check won't be the end of the world. Now for your question... I've not had much experience in using tags, but I know they're way more complicated than on SVN and are not pushed by default (as you pointed out). I've only used simple tags (ie no annotations, messages, signing etc) and haven't had many problems with it. Using them simply seems to keep things a bit like SVN, but I'm not sure to what extent. Hopefully someone else with more production use of tags will chime in too. On Wed, Jun 13, 2012 at 2:55 PM, mikelietz <[email protected]> wrote: > The upcoming official Habari addons directory will be using a post-receive > hook on Github repositories, and we'd like to use tagging to identify > released versions of plugins and themes, such that an 0.8-1.0 version of a > particular plugin (denoting that it is version 1.0 of the plugin for Habari > 0.8.x) would be available, and identified as such. > > Despite having some experience now with moving code around using git and > Github, I haven't gotten the hang of tagging so much yet. The existing > post-receive hook code (http://github.com/mikelietz/post_receive) is able > to identify a tagged commit, but in testing (often by hitting the 'test > hook' button rather than pushing commits) I haven't really seen how/when a > tag comes across. > > Also, it seems the default is to not push tags to the remote repository at > all. > > These are just things I've seen, and may not be representative of how > tagging works in the real world. Anybody have good experience with tagging > and could shed some light on a possible best practice? > > mikelietz > > -- > 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 -- Colin Seymour Blog: http://colinseymour.co.uk Tech Stuff: http://lildude.co.uk Barefoot Running: http://barefootrunner.co.uk IRC: lildude #habari -- 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
