C. Michael Pilato wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
>
>
>>If a problem is found in one of our release candidates or final
>>releases that is so bad that we would be tempted to upgrade
>>svn.collab.net, then that problem is bad enough to require us to
>>roll a new release candidate or bugfix release, at which time our
>>server can be upgraded accordingly.
>
>
> For example, this ra->get_dirs() performance death that's living in
> our 1.1.0 release. Had I upgraded svn.collab.net to 1.1.0, we'd all
> be suffering this awful performance. And why haven't we rolled 1.1.1
> with this fix?
>
I realize this, that's why I think we should have rolled 1.1.0 out on
svn.collab.net before releasing it, so we would have noticed the problem
and corrected it. I imagine that having us be exposed to the problem
directly would provide more of a motivation, and the issue would have
been corrected more rapidly as a result. As I recall this happened with
at least one release back in the day. We released a version, rolled it
out on svn.collab.net, realized some new code in the fs was unusably
slow, and fixed it. Until we rolled it out nobody had realized the
performance problem.
As for why 1.1.1 hasn't been released yet, I believe that discussion is
happening in other threads...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 10 17:17:12 2004