> The Subversion binaries for Windows won't help you much this time if you
> need it to update your apache based server: Subversion 1.2 needs Apache
> 2.0.54, but that hasn't been released yet.
> So even if there were Subversion binaries available yet, you could only
> use the client and/or the svnserve server.
Now this makes a little more sense to me. I did not know that they were
waiting for a new version of Apache to be released. This still does not
explain the other releases though. It seems like it has always been this
way.
> > I'm not ungrateful for the efforts of everyone involved here, but I am
> > just pointing out what I think is a huge hole. I mean, how are we
> > supposed to help test these releases if there aren't any official
binaries?
> Build them yourself?
Personally, I don't see how you can have a RC1 release with no binaries and
kick off a burn in period based on that. It doesn't make sense to me. If
you expect end users to build the binaries themselves and test it, well then
I guess you don't want much help testing. I run a small business and I
don't have the time to dedicate to owning this build process, but I just
can't understand how out of the 1000's of users of Subversion, no one has at
least an automated build setup for linux and windows. I can understand not
wanting to try and have automated builds for every single platform out
there, but between linux and windows, that has got to cover about 99% of the
user base.
Anyway, I'll shut up now. I'm sorry if I came across as ungrateful. I
think Subversion is by far the best SCM product out there and I REALLY
appreciate all the work that goes into it.
Thanks!
Eric J. Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 12 20:52:46 2005