I'm late to the game but have questions about plugin versioning. It seems these definitions have changed over the months/years and still contains confusion, and parts are being discussed now. So, while I am _not_ proposing anything here, I'm hoping to help clarify the current situation as specific parts. This is how I see it today (in practice):
a. Tags are used for releases. If something does not work, don't tag it (true? maybe depends on tagging scheme?) b. Trunk is for the latest development, which coincides with Habari trunk c. Version numbers live in the XML file, and do not contain Habari version numbers. So, 1.0 instead of 0.7-1.0 d. Tags are version specific releases: So, a tag might be 0.7-1.0 but not 0.7-1.x e. A branch differs, so it might be: 0.7-1.x or 0.7-2.x but not 0.7-1.0 f. Versions like 0.1.1 or 0.1-alpha are discouraged, or perhaps even illegal? Well, maybe 0.1.1 is okay? g. Not sure if we'll use -dev in trunk, but it appears not (so far), or maybe only the dist/build script will add this? or, both? h. If trunk is "0.7" then there is no "0.7" branch, yet I'm guessing at least one item above is incorrect, and a few are probably debatable. Regards, Philip -- 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
