Comments for Surround Your World http://blogs.seapine.com/jeff Wed, 20 Aug 2008 14:50:47 +0000 http://wordpress.org/?v=2.5.1 Comment on Enemies Foreign and Domestic by Opposition Research | Surround Your World http://blogs.seapine.com/jeff/enemies-foreign-and-domestic.html#comment-32 Opposition Research | Surround Your World Fri, 18 Jul 2008 15:52:53 +0000 http://blogs.seapine.com/jeff/?p=10#comment-32 [...] up. The first is that security in other products seems to be left as an exercise for the customer. I’ve talked about that before. Another area where other products take a very different approach is around triggers and alerts. [...] [...] up. The first is that security in other products seems to be left as an exercise for the customer. I’ve talked about that before. Another area where other products take a very different approach is around triggers and alerts. [...]

]]> Comment on Life on Mars by How do I know what’s changed inside the files associated with a list of issues? | Less Stress. More Quality. http://blogs.seapine.com/jeff/life-on-mars.html#comment-24 How do I know what’s changed inside the files associated with a list of issues? | Less Stress. More Quality. Tue, 24 Jun 2008 22:21:52 +0000 http://blogs.seapine.com/jeff/?p=12#comment-24 [...] from the TestTrack section of Seapine Labs in future posts. Surround SCM users should check out Life on Mars, courtesy of Jeff Amfahr, Surround SCM’s product manager, for additional Seapine Labs goodness [...] [...] from the TestTrack section of Seapine Labs in future posts. Surround SCM users should check out Life on Mars, courtesy of Jeff Amfahr, Surround SCM’s product manager, for additional Seapine Labs goodness [...]

]]> Comment on A Change Is Gonna Come by Kathy Messina http://blogs.seapine.com/jeff/a-change-is-gonna-come.html#comment-18 Kathy Messina Thu, 19 Jun 2008 21:16:47 +0000 http://blogs.seapine.com/jeff/?p=7#comment-18 We migrated some documentation from VSS to Surround to allow rapid access to it from offshore sites and over VPN. In a few rare cases I managed to import the history (because I wanted it in a few of my files). In the rest I just imported the latest. My boss was happy and I am still employed here. What more could I want? Only that our IT guys don't turn off the VSS server and wiping the drives without asking first. We migrated some documentation from VSS to Surround to allow rapid access to it from offshore sites and over VPN. In a few rare cases I managed to import the history (because I wanted it in a few of my files). In the rest I just imported the latest. My boss was happy and I am still employed here. What more could I want?

Only that our IT guys don’t turn off the VSS server and wiping the drives without asking first.

]]> Comment on Post Hoc, Ergo Propter Hoc by Marko http://blogs.seapine.com/jeff/post-hoc-ergo-propter-hoc.html#comment-12 Marko Thu, 22 May 2008 10:42:38 +0000 http://blogs.seapine.com/jeff/?p=5#comment-12 I think the most important reason to have blame feature is not to find responsible persons, but why the change was made. What I would like to see in the "blame" would be seeing the issue(s) for example TestTrack number and summary (along with date) with openable link to each change reason (to easily explore the context - what other changes were made at the same time, what versions it has been released etc). Just like Pete said, instead of having have to do the binary search manually to pinpoint the TT# when this line in question was changed the last time (and the previous etc), I really would like to see a product doing it for me. As for name, simply: "Line Change History" I think the most important reason to have blame feature is not to find responsible persons, but why the change was made. What I would like to see in the “blame” would be seeing the issue(s) for example TestTrack number and summary (along with date) with openable link to each change reason (to easily explore the context - what other changes were made at the same time, what versions it has been released etc).

Just like Pete said, instead of having have to do the binary search manually to pinpoint the TT# when this line in question was changed the last time (and the previous etc), I really would like to see a product doing it for me.

As for name, simply: “Line Change History”

]]> Comment on A Change Is Gonna Come by Daily Find #69 | TechToolBlog http://blogs.seapine.com/jeff/a-change-is-gonna-come.html#comment-11 Daily Find #69 | TechToolBlog Tue, 20 May 2008 14:37:27 +0000 http://blogs.seapine.com/jeff/?p=7#comment-11 [...] Switching source control systems?  Should you really import or start fresh? [...] [...] Switching source control systems?  Should you really import or start fresh? [...]

]]> Comment on 100,000 Airplanes by Daily Find #64 | TechToolBlog http://blogs.seapine.com/jeff/100000-airplanes.html#comment-10 Daily Find #64 | TechToolBlog Wed, 07 May 2008 16:45:25 +0000 http://blogs.seapine.com/jeff/?p=4#comment-10 [...] Jeff writes about SCM tools and auto notifications - Push verse Pull technologies [...] [...] Jeff writes about SCM tools and auto notifications - Push verse Pull technologies [...]

]]> Comment on Post Hoc, Ergo Propter Hoc by Rob http://blogs.seapine.com/jeff/post-hoc-ergo-propter-hoc.html#comment-9 Rob Wed, 07 May 2008 00:08:05 +0000 http://blogs.seapine.com/jeff/?p=5#comment-9 While blame is an often requested featue here... (usually for throwing things at people reasons) I think a better "annotate" function would be either: 1) The copyright of the code in question.. Line by Line... (maybe file by file) 2) Code Review status.. line by line. with associated comments..... Cheers, Rob Lancaster While blame is an often requested featue here… (usually for throwing things at people reasons)

I think a better “annotate” function would be either:

1) The copyright of the code in question.. Line by Line… (maybe file by file)
2) Code Review status.. line by line. with associated comments…..

Cheers,

Rob Lancaster

]]> Comment on Post Hoc, Ergo Propter Hoc by Mitch Oliver http://blogs.seapine.com/jeff/post-hoc-ergo-propter-hoc.html#comment-8 Mitch Oliver Tue, 06 May 2008 19:43:00 +0000 http://blogs.seapine.com/jeff/?p=5#comment-8 I generally seek a blame utility every time I come across a piece of code that makes exclaim something greater than or equal to "huh..." This generally falls into two use cases: "Why did we do this like this?" and "Who's fault is this?" For the former case, an interactive method of viewing check-in comments associated with a change would be very useful. I generally seek a blame utility every time I come across a piece of code that makes exclaim something greater than or equal to “huh…” This generally falls into two use cases: “Why did we do this like this?” and “Who’s fault is this?” For the former case, an interactive method of viewing check-in comments associated with a change would be very useful.

]]> Comment on Post Hoc, Ergo Propter Hoc by Pete http://blogs.seapine.com/jeff/post-hoc-ergo-propter-hoc.html#comment-3 Pete Thu, 01 May 2008 14:00:39 +0000 http://blogs.seapine.com/jeff/?p=5#comment-3 My thinking on the "blame" feature is this. If I have a reason to track down who made a change and why, having a good SCM system will give me the information I need to find out. The problem is that doing so is an arduous task involving taking various revisions of the file and running them through a diff utility until I stumble upon the changed revision (and therefore, who to blame). In today's society, if there's ever a long and potentially annoying task that *could* be done by a computer, it probably should be. My thinking on the “blame” feature is this. If I have a reason to track down who made a change and why, having a good SCM system will give me the information I need to find out.

The problem is that doing so is an arduous task involving taking various revisions of the file and running them through a diff utility until I stumble upon the changed revision (and therefore, who to blame). In today’s society, if there’s ever a long and potentially annoying task that *could* be done by a computer, it probably should be.

]]> Comment on Pilot by Grant http://blogs.seapine.com/jeff/who-is-your-daddy-and-what-does-he-do.html#comment-2 Grant Thu, 24 Apr 2008 18:25:57 +0000 http://blogs.seapine.com/jeff/?p=3#comment-2 Hey those charges were completely dropped and expunged. How was I supposed to know it was that combustible? As for that other thing, I do not recall that incident and I'm standing by that statement. Hey those charges were completely dropped and expunged. How was I supposed to know it was that combustible? As for that other thing, I do not recall that incident and I’m standing by that statement.

]]>