Indrajit,
Sorry for the very late reply :-(
2009/12/7 Indrajit Raychaudhuri indraj...@gmail.com
Grand stuff!
Thank you!
Indeed, I was wondering if we could sync this up with the Round 2 of
Refactoring exercise
(
On 09/12/09 11:01 PM, Heiko Seeberger wrote:
Indrajit,
Sorry for the very late reply :-(
2009/12/7 Indrajit Raychaudhuri indraj...@gmail.com
mailto:indraj...@gmail.com
Grand stuff!
Thank you!
Indeed, I was wondering if we could sync this up with the Round 2 of
Lifters,
Maybe you followed the discussion about the versioning policy for Lift. The
committers finally decided to have a well defined versioning policy which
you can take from here:
http://wiki.github.com/dpp/liftweb/about-versioning-policy.
Following this policy the next Lift version
defined versioning policy which you
can take from here:
http://wiki.github.com/dpp/liftweb/about-versioning-policy.
Following this policy the next Lift version will be 2.0, not 1.1, because
there are numerous changes and enhancements breaking the source
compatibility. As soon as we change
. The
committers finally decided to have a well defined versioning policy which
you can take from here:
http://wiki.github.com/dpp/liftweb/about-versioning-policy.
Following this policy the next Lift version will be 2.0, not 1.1, because
there are numerous changes and enhancements breaking
.
Following this policy the next Lift version will be 2.0, not 1.1,
because there are numerous changes and enhancements breaking the
source compatibility. As soon as we change the version numbers in the
Maven POMs, we will let you know via the lift-announce mailing list.
Best regards,
Heiko
My
versioning
policy which you can take from here:
http://wiki.github.com/dpp/liftweb/about-versioning-policy.
Following this policy the next Lift version will be 2.0, not 1.1,
because there are numerous changes and enhancements breaking the
source compatibility. As soon as we change
2009/12/7 Josh Suereth joshua.suer...@gmail.com
Just curious what the difference between Major and Minor truly is as both
can break source/binary compatibility? My feeling here is that sticking to
strick source-compatibility for minor releases is actually a bonus.
Major changes (e.g.
