git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Ralphson <mike.ralphson@gmail.com>
To: Jon Brisbin <jon.brisbin@npcinternational.com>
Cc: git@vger.kernel.org
Subject: Re: How to move users from SEU (AS400) to Git?
Date: Tue, 12 May 2009 17:40:47 +0100	[thread overview]
Message-ID: <e2b179460905120940u2d87a591kefbdf659e1badd0c@mail.gmail.com> (raw)
In-Reply-To: <1CA7E776-B216-4AA5-BFE0-63C0B066980D@npcinternational.com>

2009/5/12 Jon Brisbin <jon.brisbin@npcinternational.com>:
> Our development manager was evaluating transitioning our AS400 department to
> IBM Rational for the RPG programmers, who currently use SEU for all their
> editing and source code control.

+1 everything Shawn and Andreas said, but there are other practical
issues beyond developer mindset.

(see http://article.gmane.org/gmane.comp.version-control.git/117755
for my context)

I'm not familiar with the AS400 or SEU but do developers currently
have a complete copy of the tree to themselves, or do they only check
out the files they're editing?

I'm not sure what Rational Developer is likely to want to do in terms
of getting the edited files back to the AS400 (assuming it supports
that directly). Are you planning to run (j)git on the AS400 or have
another step to get the code from a central git repo back to the
AS400(s)?

Is any deployment done to a test server? Is there a release process
you need to integrate with?

Our devs expect their changes to go live at midnight after they
'release' them. Are there similar assumptions for you?

They also expect to see everyone else's changes (to all the source
files they're *not* working on) as soon as they go live, without
having to pull them. Madness, sure, but it's the kind of madness they
happen to want.

Previously, no-one would have had to worry about merging / integrating
(unless locks were broken). Someone (possibly everyone) now has to do
this.

Unless developers have an AS400 at home, or a very funky emulator on
their laptop, many of the distributed benefits of git are probably
going to be of no use to you.

You probably need to address what concrete benefits remain and see if
you *want* to try and sell them.

Local / feature branches, ease of moving work and history between
developers, speed, repository size, repository resilience, usable
tags, immutable history... All of those might still apply as wins in a
centralised / minimal-merging environment.

You may also want to find out if IBM can point you at a reference site
for Clearcase (presumably?) on the AS400 in conjunction with Rational
Developer on pcs. It may be so bad and so different to what they have
now, that you can push git (with a bit of scripting around it) as
actually more similar to their current workflow. 8-)

Mike

  parent reply	other threads:[~2009-05-12 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 15:42 How to move users from SEU (AS400) to Git? Jon Brisbin
2009-05-12 15:57 ` Shawn O. Pearce
2009-05-12 16:14 ` Heiko Voigt
2009-05-12 16:16 ` Andreas Ericsson
2009-05-12 16:47   ` Mike Ralphson
2009-05-12 16:40 ` Mike Ralphson [this message]
2009-05-12 17:56   ` Jon Brisbin
2009-05-12 18:13     ` Magnus Bäck
2009-05-12 18:20       ` Jon Brisbin
2009-05-12 21:31 ` Ealdwulf Wuffinga
2015-12-02 18:09   ` dleong
2015-12-02 18:22     ` Randall S. Becker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2b179460905120940u2d87a591kefbdf659e1badd0c@mail.gmail.com \
    --to=mike.ralphson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jon.brisbin@npcinternational.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).