Re: Branching for 1.3.

Could developers please look at:

   http://subversion.tigris.org/svn_1.3_releasenotes.html

If you have a 1.3-related item you're working on, please edit the page
directly (www/svn_1.3_releasenotes.html) to reflect its status.

Of the several "TODO" items on that page, these are the ones we should
resolve before branching:

   1. Brane: any news on the ".svn" / "_svn" ASP.NET front? Your post
      http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=105406
      is the latest relevant word on the subject, I believe.

   2. Am I correct that the keywords-as-hash changes are about getting
      some new APIs into 1.3, but that the feature which they will
      enable is not itself being released in 1.3?

   3. Similar story with Issue #443 (post-commit hook error output lost):
      The client-side API changes will make it into 1.3, but the bug
      itself will not be fixed in 1.3. Please correct me if wrong.

   4. The r15287 situation :-). r15287 allowed sending of multiple
      locks at once over ra_svn and ra_dav. But, it had a number of
      problems, which Peter Lundblad enumerated in his review. Since
      it introduces a protocol change, we need to either a) fix those
      problems right away, or b) yank r15287 for now, and reinstate it
      after branching 1.3, to fix at our leisure. Much as I would
      like to fix it (especially since I approved the original patch),
      I will not have time to do this before branching 1.3. If no one
      else will either, then we should temporarily revert the change.
      Thoughts? (Thoughts from Peter Lundblad especially desired...)

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org