> in my opinion it's important to release the 1.5.2 in a few weeks (of course > before the 2.0), mainly for all users that doesn't want or doesn't have the > time to migrate to 2.0, to ensure that their investment in Pivot is > preserved, and I think this is a welcome plus.
The problem is that we want users to upgrade. We're not going to maintain the 1.5.x branch indefinitely. Releasing both will simply create more work for us, and at the moment, I don't think it is justified. > I agree with Chris that it's important to provide upgrade documentation. We will definitely be doing this. > On the breaking API changes, maybe we should see if it's the case to release > this as 1.6 and not 1.5.2 ... That's exactly the problem. 1.5.2 is a bit more like 1.6 release, but it definitely doesn't make sense to do both a 1.6 and a 2.0 release. > And last, one development tasks for 2.0, I'm slowly (as always) working on > some of them (mainly the work on colors and graphics is really time > consuming, at least for me), we can update until the end of next week (and > end of next weeks too) and see what is the general status and tests. > Probably some of my tasks could be moved to 2.1 without problems (for > example the Print from Browser problem is really tricky, etc), but I'd > prefer to wait some weeks before moving to 2.1 if for others is Ok. Yeah, I imagine that there will probably be some time between 2.0 and 2.1. However, we'll probably do some 2.0.x releases in the interim. >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.
