Hi, Heiko, can you find the stated version number policies of 3 or 4 other well > regarded open source projects? That will allow us to synthesize the best of > what others have done into a coherent policy for Lift.
Take a look at the recommended OSGi version policy: http://www.aqute.biz/Code/XBnd Then take a look at Eclipse (pretty well known, eh?): http://wiki.eclipse.org/index.php/Version_Numbering Both use a major increment (1.x -> 2) to show breaking changes in API, a minor increment (1.1.x -> 1.2) to show non-breaking changes in API and a micro increment to show "internal" (no class name changes, no method signature changes, ...) changes (e.g. bug fixes in the implementation). -- You received this message because you are subscribed to the Google Groups "Lift" group. 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/liftweb?hl=.
