preliminary guide to Mercurial via workflows

[David I.]

> Can we assume that corporate developers already have a completely
configured SSH server at hand? 
> Or is it more likely that they'll use Windows shared stuff? 

I don't think we can assume in general that a central server with SSH
access is available. In my company, we have a mix of Windows and UNIX
machines so it is easy for us. If another company is Windows-only,
setting up SSH access will be a project in itself...

> I think the whole guide should also be rewritten fro TortoiseHG, so
Windows users can start with it.  

I agree. I want to transition to using HG in our group, and I really
wanted to do some workflow cheatsheets for command-line, TortoiseHG, and
Eclipse with Mercurial plugin. Since you are doing this stuff on basic
workflows, maybe I can help contribute the TortoiseHG and Eclipse
screenshots. To be complete, we should probably have Netbeans
screenshots too. Doing the documentation helps me to learn Mercurial. In
addition, I will probably use Eclipse Mercurial for day-to-day
operations, but our scripted build proceedures will only work with the
command line interface, so I need to know how to use both interfaces.

It might be helpful to scan the Bazaar workflow documentation and see if
there are any common ideas to borrow: http://bazaar-vcs.org/Workflows. 

Is your master copy published in a wiki or a repository somewhere?

David 

-----Original Message-----
From: arne_bab at web.de [mailto:arne_bab at web.de] On Behalf Of Arne
Babenhauserheide arne_bab-at-web.de |Mercurial|
Sent: Monday, May 04, 2009 12:54 PM
To: Ishee, David M
Subject: Re: preliminary guide to Mercurial via workflows

Am Montag 04 Mai 2009 16:38:54 schrieb David I.:
> I agree. It would be better to duplicate the whole BitBucket example 
> and replace all the commands with ssh commands to a "central server" 
> for a slightly different "corporate developer" workflow. Once these 
> get published somewhere, I might do that for you.

Great! 

Can we assume that corporate developers already have a completely
configured SSH server at hand? 

Or is it more likely that they'll use Windows shared stuff? 

I think the whole guide should also be rewritten fro TortoiseHG, so
Windows users can start with it. 

I assume it will even look simpler, then :) 

Luckily I can access the dialogs under GNU/Linux - only the right-click
menu is missing for me (TortoiseHG is great!)

Best wishes,
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de