Relax, Subversion *just* got a new release manager and he's getting up to
speed on the release process. :-) This is the first time that I recall them
being late on a release since I started watching this list March of last
year.
You can find the CHANGES file you seek in the online repository. Just point
your favorite browser to http://svn.collab.net/repos/svn/trunk/CHANGES. The
CHANGES file will show what was included in a release.
Someone correct me if I'm wrong, but the issues marked for a release aren't
*always* the only things that get incorporated into that release. Sometimes
other developers make some headway towards a particular feature that gets
makes it into a release. For the 0.24 release, path-based authentication
was a feature that I don't believe we had an outstanding issue on. Other
times, a problem is more involved that originally thought, or needs to be
thought out a little more due to other features being worked into SVN. The
developers generally don't hold up a release since, more often than not,
there are many other fixes and enhancements they would like to see get out
to the public. I for one, appreciate this approach. So if an issue seems
to drag, there is generally a good reason for it. These developers (and
those who participate in the community) are intensely dedicated to the
project.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 7 12:02:12 2003