(javahl) bindings maintenance

In r9017, Ben Reser and I merged a last-minute javahl bindings fix
into 1.0.1, pretty close to the release time. The fix, however, had
been known since r8652 (r9017 is really just McClain Looney's backport
of the crucial part of r8652).

I'm wondering, is there some way we can make it easier to catch such
problems earlier? If it would help, we could make it part of the
release process to send out a reminder to try building the bindings on
the soon-to-be-released branch. If we did that the moment we set the
date for a release, then bindings fixes could come in much sooner.

If all bindings maintainers read the dev@ list regularly, then we can
just post the reminder to dev@. Or if not, then we should work out
something else.

Please let me know your thoughts. Last minute backports like this are
eminently avoidable, if we plan ahead a little more...

Thanks,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 12 19:30:54 2004