Josh, Thank you for your brilliant elaboration of compatibility issues!
2009/11/22 Josh Suereth <[email protected]> > The real question is, with all these breaking changes in lift 1.1, has any > attempt been made at source-compatability? If not, I would argue a bigger > version jump than 1.1. > The current Lift is not source compatible with 1.0.x, just consider Box moved from ...util to ...common. Hence you would go for 2.0, right? > Also, there is the possibility of taking the version system and adding a > "functionality milestone" version at the begginning. In this case, you can > use that number for marketting purposes (e.g. "Lift goes 1.0!). Your > version number would then be <Marketing>.<SourceCompatability>.<All but > Trait BinaryCompatability>.<Binary Compatibility>. > I am all against using versioning policy for marketing! 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=.
