On Sat, Nov 21, 2009 at 4:29 AM, Timothy Perrett <[email protected]>wrote:
> Heiko, > > Sounds pretty rational - couldn't agree more that we need a suitable policy > in place. > 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. > > Cheers, Tim > > On 21 Nov 2009, at 08:27, Heiko Seeberger wrote: > > > For me it is important that there is a version policy in place, such that > everyone knows what's the difference between a change to 1.1 or to 1.0.2. As > we probably will stick to Lift 1.1, IMHO the version policy has to be: > "Increasing the major or minor version number means breaking changes, > increasing the micro version number keeps the API stable.". Opinions? > > > > -- > > 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=. > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- 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=.
