On Fri, Feb 20, 2004 at 11:44:38AM -0600, firstname.lastname@example.org wrote:
> I'd like to get the language bindings out of the core Subversion tree
> and into their own project.
I agree about separating the development process and schedule. But I
think Subversion should ship the bindings by default. This makes it
easier for end users to get them work, and thus encourages people to
write extensions with bindings. People who want or need to use the
latest bindings code should be able to know what to do with
In this case, I'd like to propose branching the development of each
bindings (either on the same svn server or another). This would ensure
the developers a usable tree, while api incompatibility hasn't be
merged from trunk. And the maintainer is responsible for integrating
the bindings change back to trunk, respecting the core's development /
release schedule. If there are supplement releases they should be made
as subversion-bindings-x.y.z as described, containing only the
I know this is getting closer to a development model ghudson opposes,
but it seems to be the most reasonable and viable way to me.
Additionally this makes it easier to port bindings enhancements to
older subversion core as supplement releases.
Received on Sat Feb 21 10:22:07 2004
- application/pgp-signature attachment: stored