On Sat, 30 Jul 2005, Lieven Govaerts wrote:
> My goal was not to have the XSD file in the svn repository per se, I
> have a public svn repository myself, so that's not the issue.
>
I see. I was mostly replying to Julian here. My point is that it is better
to have no schema than an out-of-date one, so we need someone that can
maintain it. If you're committed (you can even get partial commit access
to the svn repository if that seems the most practical solution after some
time) then I'm OK with having it in the repository (even if I'm more an
RELAX NG person:-).
> Since I will be using this XSD myself to build a web-based reporting
> application for the company I work for, I'll have to keep this XSD
> updated anyhow. My only problem is that I now have to check each new
> release of subversion to see if the logging code has been changed.
> It would be easier for me if someone of the developers group would
> be involved in this, that's all.
>
I think looking at the CHANGES file for new releases should be enough. We
should document changes to the ouput format there. Also, the output
changes normally only in 1.x.0 releases.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 30 22:50:21 2005