[Proposal] Close 1.5 branch and create another branch

[Andrew C. Oliver]

Hi all,

This is primarily an HSSF concern

I'd like to submit that we close the 1.5 branch. The bugs are *well known* and I don't think anyone here plans to do any 1.5.x based fixes anytime soon.

I'll be launching a new project called Enterprise Reporting System (for lack of a snappy name) soon. While I'm certainly not leaving (and ERS will depend on POI), I want to get my major effort (probably the most drastic code I've written on POI in the last 6 months) out of the way before I get too involved in creating the new community.

To this effect, I think I've changed my mind about my earlier refactoring. While in one respect it makes things harder to debug, in another it makes them easier. I think my difficulty was that I was strictly working on the stuff that got harder. The rest of the stuff is actually cleaner and easier and clarifies the original intended seperation of our object model (usermodel was supposed to be a LIGHT wrapper around mode). The product I'd like to develop around HSSF never required me to keep this to myself, I just had to think about whether it was the right time to do this for HSSF.

However, I don't want to disrupt things as its a MASSIVE change; which,
is part of why I want to get it in sooner rather than later (more work to merge later). So what I'd like to do is create a 3.0 branch where I can apply these changes without disrupting the other work. In the end if everyone things my approach is goodness then we'll just merge the two
and move on.

To avoid confusion I'll make the nightly builds go against the 2.0 branch and probably upoad the data on the other branch elsewhere.

Certainly anyone else wanting to try something radical could work in the same branch as I. In particular Avik, you might want to do your formula refactoring there...

Any thoughts on this?

-Andy




--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>