subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhuij...@apache.org
Subject svn commit: r1462060 - /subversion/site/publish/roadmap.html
Date Thu, 28 Mar 2013 12:00:55 GMT
Author: rhuijben
Date: Thu Mar 28 12:00:54 2013
New Revision: 1462060

URL: http://svn.apache.org/r1462060
Log:
* roadmap.html
  Mark the profiling step of new apis as completed. Over the last few months
  I profiled all the cases I profiled before (status, update, merge, copy,
  etc. etc.) and found no new problems.
  
  Of course we can always improve further, but the original db query work I
  did earlier in 1.8 development and the verifications added back then now
  show a lot of improvement over 1.7 and no recent regressions.
  
  I call this done for 1.8. And if we find and solve new problems we can try
  to backport them.

Modified:
    subversion/site/publish/roadmap.html

Modified: subversion/site/publish/roadmap.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/roadmap.html?rev=1462060&r1=1462059&r2=1462060&view=diff
==============================================================================
--- subversion/site/publish/roadmap.html (original)
+++ subversion/site/publish/roadmap.html Thu Mar 28 12:00:54 2013
@@ -371,9 +371,9 @@ numbering, compatibility, and deprecatio
     <td>Review private APIs (including APIs used by <tt>subversion/svn*/</tt>),
         and determine which of them should be promoted to public.</td>
   </tr>
-  <tr class="task-level-2 not-started">
+  <tr class="task-level-2 completed">
     <td class="task-name">API performance analysis</td>
-    <td class="task-status">Not&nbsp;Started</td>
+    <td class="task-status">Completed</td>
     <td>Profile the new APIs to determine which can/should be optimized.</td>
   </tr>
   <tr class="task-level-1 in-progress">



Mime
View raw message