OK, that seems fine. Why don't we start the release process for 1.5.2 now, and we'll start the 2.0 release in a couple of weeks. That way, we'll get 1.5.2 out of the way, and we can make it available for some limited period of time afterwards (a few months or so) - with the understanding that it is no longer being maintained.
On Sep 24, 2010, at 11:47 AM, Sandro Martini wrote: > > Hi Greg, > >> From what I can tell, a number of developers have already started working >> with 2.0 or have at least started looking into it. In the long run, I >> don't think we'll really be helping anyone by continuing to support 1.5.x. > I agree with you, this (1.5.2 or 1.6, no matter) could be the last 1.x > maintenance. > > And I agree that it's more important to avoid confusion in users, so maybe > the only option to get it could be to release it fast, in 1 or max 2 weeks > (maybe before if possible ... if all tickets are closed we could already > start to do some stress test on it), so even all our work (most of it yours > :-) ) on it would not be wasted. > > Sandro > > -- > View this message in context: > http://apache-pivot-developers.417237.n3.nabble.com/Pivot-2-0-tp1573464p1574790.html > Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
