> Anyway, my real question: How do we name versions that are in > development? > > Say I have a 0.7-0.1 plugin, and I tag it. That's fine. > Then I start working in trunk on 0.7-0.2. I don't want to actually > name it 0.7-0.2 yet because I want the version number to be distinct > from the _actual_ 0.7-0.2 (the one I'll eventually release). > > In PHP/PECL, we'd name this "0.2-dev". Is 0.7-0.2-dev too cumbersome? > > Other ideas? I'm open to anything, but I do think we should all follow > the same scheme.
Discussed this on IRC a bit. http://drunkenmonkey.org/irc/habari/2009-11-19#T05-54-50 We're thinking that the -dev suffix could be painful. An idea that kicked around: adding a way to specify that a plugin is unstable to the .plugin.xml. <version>0.2</version> <unstable/> or even <version stable="false">0.2</version> Thoughts? One other question that came up: Are plugins versions declared as "0.7-0.2" in the XML? or is the 0.7-0.2 convention just for tags? If the former, might it make more sense to split the two distinct pieces of data into two elements? <version> <habari>0.7</habari> <plugin>0.2</plugin> </version> (the tag would still be 0.7-0.2) Just kicking around ideas; not trying to promote an agenda. 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
