You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Shahaf <da...@elego.de> on 2013/03/29 07:22:39 UTC
Re: svn commit: r1462060 - /subversion/site/publish/roadmap.html
rhuijben@apache.org wrote on Thu, Mar 28, 2013 at 12:00:55 -0000:
> 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.
>
To clarify, did you profile only new-in-1.8 libsvn_client APIs, or did
you profile new APIs in other libraries too?
> 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 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">
>
>
Re: svn commit: r1462060 - /subversion/site/publish/roadmap.html
Posted by Stefan Sperling <st...@elego.de>.
On Mon, May 13, 2013 at 04:27:03PM +0300, Daniel Shahaf wrote:
> James Hanley wrote on Mon, May 13, 2013 at 09:18:36 -0400:
> > Is there any insight to update the projected (or goal) release date for 1.8
> > as right now it indicates "Q4 2012 *(Unconfirmed)*" which has come and
> > gone...
> >
>
> If all goes well, the process will be:
>
> - Roll 1.8.0-rc2 for developer testing.
> - Get signatures on it.
> - Release 1.8.0-rc2 publicly.
> - Wait four weeks, during which no show-stopper bugs are reported.
> - Release 1.8.0.
>
> (as per http://subversion.apache.org/docs/community-guide/releasing)
>
> So that adds up to a lower bound of five weeks. I will not offer
> a prediction as to an upper bound - that depends on how many
> show-stopper bugs surface.
If things turn out really well we might be able to release in 4 weeks
during the hackathon in Berlin, and have a release party there:
http://www.elegosoft.com/en/company/news/news-in-detail.html?tx_ttnews[tt_news]=142&tx_ttnews[backPid]=254&cHash=2d372c9714f33264eea41b6c9433d740
Not quite sure if we'll want to adjust our release schedule to match
that opportunity, but I would say it's worth considering :)
Re: svn commit: r1462060 - /subversion/site/publish/roadmap.html
Posted by Daniel Shahaf <da...@elego.de>.
James Hanley wrote on Mon, May 13, 2013 at 09:18:36 -0400:
> Is there any insight to update the projected (or goal) release date for 1.8
> as right now it indicates "Q4 2012 *(Unconfirmed)*" which has come and
> gone...
>
If all goes well, the process will be:
- Roll 1.8.0-rc2 for developer testing.
- Get signatures on it.
- Release 1.8.0-rc2 publicly.
- Wait four weeks, during which no show-stopper bugs are reported.
- Release 1.8.0.
(as per http://subversion.apache.org/docs/community-guide/releasing)
So that adds up to a lower bound of five weeks. I will not offer
a prediction as to an upper bound - that depends on how many
show-stopper bugs surface.
Re: svn commit: r1462060 - /subversion/site/publish/roadmap.html
Posted by James Hanley <jh...@dgtlrift.com>.
Is there any insight to update the projected (or goal) release date for 1.8
as right now it indicates "Q4 2012 *(Unconfirmed)*" which has come and
gone...
On Fri, Mar 29, 2013 at 2:22 AM, Daniel Shahaf <da...@elego.de> wrote:
> rhuijben@apache.org wrote on Thu, Mar 28, 2013 at 12:00:55 -0000:
> > 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.
> >
>
> To clarify, did you profile only new-in-1.8 libsvn_client APIs, or did
> you profile new APIs in other libraries too?
>
> > 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 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">
> >
> >
>