[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Taking Issue 45

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-06-25 11:04:49 CEST

Stefan Fuhrmann wrote:
> Hi @dev!
> As the days just started getting shorter and
> with the 64 bit port got finished, I was thinking
> of taking "log caching" as my next project.


> My design efforts are initially targeted on
> the storage layer and I think I already solved
> some of scalability issues. The goal is being
> able to handle KDE.org-sized repositories
> within reasonable time and space. But it is
> surely a very complex matter (e.g. following
> renames etc.)

Don't forget to assign the issue to yourself

(login sent to you via PM)

> Target would be 1.5.0 (spring 07?).
> Any objections?

No objections at all.

One thing we have to discuss though is how we should handle this. Right
now, trunk is for the upcoming 1.4.0 release. We have to create a new
branch for this. Question is now what the branch would be for: 1.4.x or
1.5.0. If the branch would be for 1.5.0, then we'd have a lot of merging
to do from trunk to 1.5.0 to keep it in sync until we branch for 1.4.x.
If the branch is for 1.4.x, then we have to merge a lot of fixes from
trunk to it.

So, what would be the best approach here?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Jun 25 11:04:59 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.