Re: How to manage one project but wtih two repositories

Mark Breen wrote:
> Hello All,
>
> We are using SubVersion and TortoiseSVN for a Visual Studio 2008
> project as part of a small 5 - 20 person team. This is a
> non-commercial pilot project with the primary aim to develop our
> scrum / agile development skills.
>
> We do all our development work on a private server that I maintain,
> and it works very well for all the members of the team.
>
> Approx twice per month, we try to post our latest version of code to
> a public SVN site, www.Codeplex.com
>
> On this public site, we allow many more people to connect and
> download our source code, last time we updated the code, we had 500
> downloads.
>
> Sorry to for the long winded introduction, but now I can state our
> problem.
>
> What is the best approach to keeping the public site updated
> periodically.
>
> In other words, we commit on a daily basis to our private server used
> by 10 - 20 people, but once or twice a month, we can to make a
> snapshot of that code and {Commit / publish / replace} the code on
> the public site.
>
> Up to now, our main developer has done this sort of manually, but it
> is taking him two to three hours.
>
> I initially thought about the following steps
>
> 1) export all code from the working folder of the private repository
> 2) check out all code from public site 3) delete all code from
> working folder of public site 4) paste previously exported files from
> step 1 5) commit all files back to public site.
>
> This seems all wrong however, and I doubt it will work. I assume
> that there must be a better way, perhaps using branches, but I am
> really not sure what is the best way to do it.
>
>
> Is my question even clear here? if not please post back and I will
> try to expand on which aspect is unclear, or better again, i will
> have to re-write the whole question.
>
> Thanks in advance for your assistance, as always on forums, I
> appreciate your time.

Codeplex allows access with svn clients. So why don't you just commit to
the repository there?

Or maybe use another hoster like sourceforge, tigris.org or google code.
At least with google code, you could still host your repository locally
and just use svnsync to synchronize your local repo with the one hosted
on google code. (codeplex doesn't allow svnsync, not sure about
tigris.org - but google code and sourceforge allow svnsync).

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2357487
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].