In that case, this seems like a more sensible method of tagging than trying to keep up with each pre 1.0 release.
+1 to the system and adding the <requires> to .9 On Wed, Jun 13, 2012 at 11:50 AM, Owen Winkler <[email protected]> wrote: > On 6/13/2012 11:43 AM, Michael Bishop wrote: > >> >> >> On Wed, Jun 13, 2012 at 11:30 AM, Owen Winkler <[email protected] >> <mailto:[email protected]>> wrote: >> >> . >> Consider an example: >> >> The Coffee plugin releases a version 1.0 for Habari 0.8. The tagged >> version is 0.x-0.8. It does not require any specific feature of >> Habari that is not available as of the plugin release, so no >> <requires> elements exist in the plugin xml. >> >> >> Just so I understand, did you mean it would be tagged 0.x-1.0 or 0.x-0.8 ? >> > > > Oops, I meant "0.x-1.0". "0.x" is the compatible major Habari version and > "1.0" is the version of the plugin. > > Thanks for picking up on that -- I'm glad someone was paying attention. :) > > > Owen > > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to habari-dev-unsubscribe@** > googlegroups.com <[email protected]> > For more options, visit this group at http://groups.google.com/** > group/habari-dev <http://groups.google.com/group/habari-dev> > -- 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
