> > I think version numbers are idiotic, and created by the marketing > department, and not engineers. >
I strongly disagree: An appropriate version strategy is not at all about marketing but expresses valuable information. In OSGi increasing the major version means breaking changes in the API, increasing the minor version means nonbreaking changes in the API and increasing the micro version means no changes to the API but only changes of the implementation. Further these versions are used to declare dependencies between modules (OSGi bundles) which results in a high degree of trust that different modules work seamlessly together. As Lift also is to support OSGi (already some support in place) it would be beneficial to stick to this version policy. I think a 2.0 needs more time with a 2.0 mindset. Once 2.0 is on the table there may be more redesign involved. I disagree: Versions should not express a mindset but information about (non)breaking API changes. That's all, no magic, no marketing, no mindset. Heiko Seeberger My job: weiglewilczek.com My blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- 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=.
