Comments on: Stream-per-Task Pattern – with AccuRev SCM

By: Security Primer - Anatomy of the AccuRev Admin Trigger « Software Configuration Management

Fri, 27 Mar 2009 16:45:38 +0000

[...] you read the private prototyping or stream-per-task blogs by Dave Thomas? These are good examples of how dev teams and developers control how their [...]

By: Pattern for Private Prototype Development « Software Configuration Management

Thu, 13 Nov 2008 16:10:20 +0000

[...] stream that will collect all changes from your entire team. [See related blog, Stream-per-Task Pattern]. The majority of team members may have their workspaces directly from here. Next, create a [...]

By: Developing in streams, releasing from streams « Software Configuration Management

Thu, 25 Sep 2008 17:27:06 +0000

[...] with the idea of dedicating an SCM construct per-feature, there are plenty of people who do. (See Stream-per-task paradigm, for example by Dave Thomas). But that’s not the point. Whether you put one feature or ten in [...]

By: Retargeting Features to Future Releases « Software Configuration Management

Retargeting Features to Future Releases « Software Configuration Management — Fri, 25 Apr 2008 17:08:49 +0000

[...] feature streams to isolate [...]

By: Pattern for Stable Development « Software Configuration Management

Pattern for Stable Development « Software Configuration Management — Thu, 27 Mar 2008 20:36:40 +0000

[...] be obtained by simply setting a time rule on your parent stream! This works best if you have a stream-per-task paradigm so the time rule only affects your (team’s) active development. The idea is simple – anytime [...]

By: Sean

Sean — Sun, 09 Dec 2007 02:04:17 +0000

Unfortunately upon further inspection it appears that although you have private workspaces, their versioning has to happen on the ‘mother ship’ which is a non-starter for some one who needs the flexibility of disconnected versioning like you can do with GIT and Mercurial. My developers cannot be tied down to a server connection. We use laptops, we travel, we develop. It is a pity you don’t have the ability to keep the store and meta on the client side.

Please correct me if I am wrong.

Sean

By: Sean

Sean — Sun, 09 Dec 2007 01:09:25 +0000

I see a lot of similarity with other distributed version control systems. How does Accurev differ from GIT or Mercurial?

Sean

By: davidpthomas

davidpthomas — Wed, 24 Oct 2007 01:24:32 +0000

That’s a great idea! What about creating a pass-through stream for this purpose? This way you can visually see who-is-working-on-what, without requiring a potentially unnecessary promote step…

By: Mike Coon

Mike Coon — Tue, 23 Oct 2007 22:33:48 +0000

How about creating the streams automagically when the defect or feature is created? Is there a downside to auto creation?

Mike