On Fri, Aug 28, 2009 at 10:31 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> >this "old repo" was dumped before the upgrade and loaded into the prod
> server that is still 1.4.2. We want to take the "prod server data" >that is
> 6 months newer than the orginal dump and puit is back onto the test serfver
> that was updated to 1.6.5 but still has the orginal 1.4.2 >repo on it.
> That's not a problem. You can dump the 1.6 repo and load it on the 1.4
> >>I think you need to determine if there is really a valid REASON to do
> this. They do realize that 1.4 clients will still work with 1.6
> >This is my delima thay don't believe it, they are using SCCSVN 1.5.x and
> Tortoise 1.5.x and are afraid since it works with their 1.4.2 >Repository
> and Server that updating the server to 1.6.5 will somehow cause there svn
> apps to stop working.
> Seeing is believing. They can certainly access a 1.6 server/repo with 1.5
> clients. Why don't they just check out stuff from the 1.6 server and see?
> Also, I don't understand why you have two servers with the same repository?
> Why not just have the test repo on the same server as the production repo?
The reason for 2 servers is we test on the test box and it is also a
training system for those folks just learning subversion.We have very strict
security issues and have to maintain 100% uptime in production whereas the
test box is crash and burn more or less.
If an upgrade crashes we might affect other production applications, we are
talking thousands of apps. in daily use.
" The fundamental principle here is that the justification for a physical
concept lies exclusively in its clear and unambiguous relation to the facts
that it can be experienced" AE
Please Feed and Educate the Children... it's the least any of us can do.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-28 16:55:11 CEST