The real question is could you still keep source compatibility if you made use of some interesting implict and @deprecated annotations? I believe those are acceptable.
- Josh On Mon, Nov 23, 2009 at 6:05 AM, Timothy Perrett <[email protected]>wrote: > Interesting - this is something i've not actually thought about: If we were > to compile a list of all the breaking changes in 1.1, perhaps that would > give some focus to this discussion... as josh points out, there are most > likely quite a few now and 1.0 -> 1.1 is a fairly short jump. > > Loc and LocParam > Actor -> LiftActor > Full,Box etc have moved packages > JSON parsing alterations and changes in JsExp > > Im probably missing a number of others, but we are talking about some > fairly significant breaks here, right? > > Cheers, Tim > > On 23 Nov 2009, at 07:09, Heiko Seeberger wrote: > > > 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]<liftweb%[email protected]> > . > > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=. > > -- > > 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]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=. > > > -- 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=.
