3 ms·

I've worked in a couple of companies that did this. We had the following flow and it worked great: Task assigned to developer via email, developer takes curren

by b0 14y ago

I've worked in a couple of companies that did this. We had the following flow and it worked great: Task assigned to developer via email, developer takes current release tar from ftp and untars, does work, creates patch, forwards patch to colleague to review, forwards to release manager who integrates all incoming patches, drops into a new tar, releases to ftp. Some of this was automated with a few hundred lines of perl. The rest was on a whiteboard.

raverbashing 14y ago
Interesting They could skip the ftp part, because git saves bandwidth Still, this is a good way to do the work
- b0 14y ago
  They use scp now rather than ftp. They don't use git because it's too complicated for contractors to handle.