> >c) Release the slide version as 1.0 and the refactored version as 2.0.
> >Version 2.x continues as the main and 1.x as a branch. This is the same
> >as option a, some people will continue to use 1.x and some will use 2.x
>
> If the sole or primary reason for a 1.0 release is compatibility with
Slide,
> then it seems a bit silly to me to pretend that it is anything but a Slide
> release. On the other hand, such a release is not so silly that it's
worth
> the negative aspects of the other options. So my preferences would also
be
> C or A, in that order. In my mind neither B nor D are workable solutions.
It's not _JUST_ a Slide release. Slide is the most visible, but the
intention is to have a release of the code as it existed in Slide.
This is because a lot of other code does depend on it at an API level and I
am sure (as I am one of them) those people would like to have a released
version, even if it is just to have a downloadable jar somewhere. I as a
consumer of the 1.0 release am pro-1.0 as I would like at least some of the
changes that you have made, but at this point have too many irons in the
fire to go back and change the API ;-)
Scott
