On 7/13/06, Jean T. Anderson <jt..ristowhill.com> wrote:
> Mike Kienenberger wrote:
> ...
> > I also think that the unique situation that we're in with regards to
> > releasing Cayenne 1.2 justifies the delay in getting our external
> > resources merged into the incubator. We've been working on Cayenne
> > 1.2 for a year and a half. We've been a podling for three months.
> > Alienating our community just to expediate our incubation seems
> > counter-productive.
> >
> > So it's not a girlfriend holding up the wedding so much as a pending
> > divorce. :-)
>
> ouch! I think we need a different analogy. Divorce sounds so ....
> acrimonious. Maybe compare it to a move from Madrid to Geneva, or
> Chicago to Mexico City. The address definitely changes, as do some of
> the customs -- although less so with Cayenne because it started off as
> an open source project.
>
> Alienating a user community would never be desirable. For whatever it's
> worth, the Derby user base experienced significant changes between the
> old Cloudscape product and the first Derby product that went beyond just
> the namespace change to org.apache.derby. I hope none of them felt they
> were caught in the middle of a divorce! But I do know there was some
> scrambling to catch up.
What I'm trying to say (and maybe I tried to be too "cute" about it)
is that delays are due to pending tasks that must be finished (release
of objectstyle cayenne 1.2) to close out the objectstyle side of the
project. These tasks are going to be finished at some point --
there's a definite ending point -- but that date was intentionally
vague since we weren't able to predict when the product was
release-ready. These tasks are also essential (we're not going to
require our userbase to completely retrofit their applications to the
apache namespace just to use the final release for Cayenne 1.2).
The post by Jim makes it sound like we're intentionally dragging our
feet when in fact we're all very eager to finalize this release and
move on.
I also think the objectstyle community and the apache community are so
similar that I don't any issues for our user-base. The changes are
technical (svn instead of cvs, etc) and procedural (some things are
more formalized, but what's being done hasn't really changed) on the
dev side.
And just for anyone who missed the other thread, it sounds like the
release is going to happen over this weekend.
This archive was generated by hypermail 2.0.0 : Thu Jul 13 2006 - 16:01:17 EDT