We kind of broke it already. Currently it looks broken in either way to me. I think we should try for the best possible fix that has clear semantics and an "easy-enough" migration path.
I'd also suggest to discuss this further in the mentioned JIRA ticket to have a straight issue history. - René Am 07.11.2014 22:02 schrieb "Paul Benedict" <[email protected]>: > I'd rather break everything at once. That's how I feel about it. I don't > want to keep on telling users migration plans from 2.3 to 2.5 and 2.5 to > 3.0 > > > Cheers, > Paul > > On Fri, Nov 7, 2014 at 8:59 AM, Lukasz Lenart <[email protected]> > wrote: > > > 2014-11-07 15:56 GMT+01:00 Paul Benedict <[email protected]>: > > > I keep telling Lukasz we need to build 3.0 -- but he hasn't taken my > > advice > > > yet :-) > > > > We can skip 2.5 if you think that's better - but we will have a lot of > > changes at once > > > > > > Regards > > -- > > Łukasz > > + 48 606 323 122 http://www.lenart.org.pl/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
