SVNBook 1.8 status
C. Michael Pilato
cmpilato at red-bean.com
Thu Mar 3 07:15:21 CST 2016
In my experience, the read-through process can produce a fair amount of
change. Any change made after the branch is a change that's likely to
require porting. So, I generally would encourage the read-through first,
then the branch.
On Wed, Mar 2, 2016 at 12:34 PM, Pavel Lyalyakin <
pavel.lyalyakin at visualsvn.com> wrote:
> As far as I can tell, the current list of tickets on Milestone en-1.8
> <https://sourceforge.net/p/svnbook/tickets/milestone/en-1.8/> is in line
> with SVN 1.8 Release Notes. What is more, most of the tickets have been
> (somewhat) resolved and have status "fixed" at them moment. There are still two
> open tickets #263 & #240
> I guess that we could begin read-thru or skip it and just make a branch of
> SVN 1.8 to begin working on SVNBook 1.9.
> Any ideas or recommendations?
> With best regards,
> Pavel Lyalyakin
> VisualSVN Team
> svnbook-dev mailing list
> svnbook-dev at red-bean.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the svnbook-dev