We’re very excited to release QA Wizard Pro 2010.1 to beta today! The beta is open to anyone, so feel free to click through and try it out. If you do try it out, please leave feedback so that we can continue to improve our product offerings.
Continue reading…
Recently, you may have read about some security attacks against large companies like Google, Adobe and others called Operation Aurora. You may have also seen that the underlying attack was against their SCM systems. McAfee published a white paper on this topic (found here) that outlines some of the problems with the SCM system in question. Continue reading…
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponCustom fields allow you to define metadata you want to capture about a file beyond the normal information (like last date modified) that Surround SCM inherently tracks. Each field can be typed as text, integer, float, list, SCM users, date/time or check box. You can also set default values for any of these.
By themselves, custom fields let you do some useful things. For example, Surround ships with a custom field called Owner, which is a drop-down list of your users. As a team lead you can grab groups of design specifications and, with one click, assign those files to an engineer to manage.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWorks with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
This is an example of how to use the Surround SCM API to synchronize a local folder with a repository. It came as a request from one of our documentation folks, who use a tool to produce our HTML files and then need to pump the output of that tool into an existing repository.
Basically, we get a list of the files and directories and check in any existing files, add new files or repositories, and delete old files and repositories.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponSurround SCM provides complete control over software configuration management processes. With its advanced feature set, including support for parallel development, automation capabilities, and extensive IDE integrations, setting up Surround SCM for your environment may seem like an overwhelming task. The following tips can help you set up Surround SCM to ensure maximum efficiency in your development organization.
Continue reading…
Works with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
This is a Mac version of the Launch Outlook example. In this example, we’ll use Applescript to attach the files. The AppleScript is a little more complicated, as we have to handle the various ways that the results can be passed in (see the original article for the details.)
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWorks with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
Overview
This is a short sample showing how to leverage the new client menu integration in Surround SCM 2010 and AppleScript on the Mac. This sample shows how to add a file context menu item which copies the sscm:// path to the clipboard for pasting into another application. The XML file for the menu is simple enough (Please refer to the Surround SCM Custom Client Menus article for help on creating a custom menu option to access the tool)
Continue reading…
Works with Surround SCM 2008
We have a large number of customers who move to Surround SCM from Subversion. One of things they look for is a way to “convert” their existing data to Surround. In general, our experience has been that this may not be the best answer. When you move to a new SCM system, you want to structure the data in way that takes advantage of the new system. In addition, it’s not possible to move the data over with perfect fidelity. The concepts in one system rarely map perfectly to the new system.
With all those caveats, I’ve created a script to assist in migrating to Surround from Subversion.
Continue reading…
One of the things I do is look at competitive products. I do this both to understand their strengths and weaknesses as well as our own. Looking at someone else’s solution to a similar problem can often give you a fresh perspective.
As I looked at several of these, a few trends showed 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. This is another part of an application that either isn’t shown in a demo, or if shown the trigger is already installed and working. The user sees that emails are being generated or actions are being triggered with an aside of “all this and more can be yours with just a little script writing.”
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponAs a Macintosh user it’s easy to feel left out by cross platform application vendors. Microsoft is too easy a target (though I can’t miss the chance to say I use Entourage every day and it never ceases to make me angry), so I’ll pick on someone my own size. Seapine. Although we have a fully native (that means not Java, you cheaters. You know who you are) client and servers on Linux, Solaris, Mac and Windows we don’t always make them, well, native enough. Make all the command keys match common conventions on that platform. Take advantage of platform specific technology, or the latest UI craze.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
