Hi Kim,
Kim van der Linde wrote:
Mark,
Open source principles.
I agree with the principles, but IMHO, there are several issues with this release that are to fundamental to be released.
You should think of the "release" as "after the fact", it is a snapshot of our past years effort unto this point so that we may start "anew" with ideas such as your own concerning the Matrix and Variance classes etc. A project should release after a significant period of "stability" and use these periods of "stablity" to indicate that it is time to release. We have been stable for almost the entire summer up to this point. Its time to cut a release and then get adventurous again.
I expect we will "1.0 branch" the cvs at the point where we are releasing to do bug fixes against it, then merge the fixes into the "trunk" this frees the trunk up to be more aggressively developed.
I agree (strongly) that we need to get a release cut for the reasons that you have given; but IMHO a release represents a commitment to the API. If we are not happy enough with the public API (including packaging) that we are willing to support it fully (i.e. maintain backward compatability for the forseable future -- at least until 2.0), we should make the necessary changes *before* release. Don't get me wrong -- I am looking forward to extending and innovating beyond the existing code base as much as anyone. I just want to make sure that we all on the same page regarding commitment to the release. If we need to change package structure or interfaces, we should do it now.
My +1 on the release means that I am perspnally happy enough with the API that I am willing to support it, working within the restrictions that it imposes for existing things, and I think it is a solid enough base to build on. If others disagree, we need to come to consensus, make the necessary changes and release an API that we are all comfortable supporting.
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
