Posted by Jeremy
Tue, 12 Feb 2008 19:48:00 GMT
SourceGear will be at the SDWest trade show on March 3-6 in Santa Clara, CA. Please come see us there at booth #308. I’m really excited to get out and talk directly to customers, and to show off some of the features that set Vault and Fortress apart from the rest of the pack. I’m also excited because we’re having a contest to give away Fortress licenses to anyone who can defeat me at Guitar Hero.
In between practicing Guitar Hero, we’ve entered code freeze for the 4.1 Vault and 1.1 Fortress release. Testing is going well, and we’re very grateful for the comments and suggestions that we’ve gotten from our beta users. In less than two weeks, everyone will be able to enjoy the features that only the beta testers have seen so far.
Posted by Paul Roub
Thu, 17 Jan 2008 14:27:00 GMT
The new betas are out! Fortress 1.1 beta 2 and Vault 4.1 beta 2 were released yesterday – see the release notes here, download Fortress 1.1b2, or download Vault 4.1b2.
Vault Changes since Beta 1:
- VS.Net Context Menus: The VS.Net Client’s context menus were rearranged in order to provide easier access to commonly used operations.
- Better progress indicators In the VS.Net client: The Add Solution and Check In commands now give status as to what is occurring.
- Refresh Source Control Status: In the VS.Net client, there’s a new menu item in the File->Fortress submenu to refresh all source control statuses to update file icons in the Solution Explorer.
- New Look: After 5 years with the same icons, Vault now has a new icon set.
- 64 bit support: We’ve corrected the installer issue that was preventing server installs on a 64 bit OS. IIS will still need to be put into 32 bit mode.
- Project Rename: Projects can now be renamed in the Visual Studio client.
- Fix for an unregistered dll: Numerous people upgrading from the 4.0 client to the first 4.1 beta noted exceptions caused by an unregistered dll. This beta should fix those issues.
- Fixed Eclipse 3.3 thread access errors: Eclipse 3.3 caused some problems on startup, giving a thread access error.
- Other bug fixes: Lots of other minor tweaks and fixes to issues reported in Beta 1.
Fortress Changes since Beta 1:
- New GUI based work item tracking window: The new work item tracking window allows you to query, add, edit, and browse work items without leaving the Fortress Client. Also, the new work item tracking window provides all of that capability while browsing for bugs to update with a source control check in.
- Image Paste and Edit: The Image paste and edit functionality which was only available in the Eclipse client for the first beta is now available in the Fortress Visual Studio client and the standalone GUI. In addition, work item attachments can be added by dragging files onto the attachment control.
Posted by Jeremy
Fri, 28 Dec 2007 15:28:00 GMT
SourceGear recently sent out the first of its quarterly newsletters. Since this is the first mass mailing we’ve done in a long time, we keyed it off of the email addresses we had in our sales system. Since in some companies the person buying Vault may not be the person using Vault, it’s worth it to mention the newsletter here, to see if any developers and managers missed out on it. You can read the first newsletter here.
Some guidelines we tried to follow:
- The newsletter should not be too frequent. Quarterly is enough.
- The newsletter should be informative. The first one has a feature on the new Image Paste and Edit feature that’s in the Fortress Eclipse client in beta 1, and coming for the Visual Studio client and the standalone Windows GUI for beta 2.
- Communication is a two-way street. We want to hear from customers, and have included a poll in the newsletter, as well as a direct email address for the newsletter’s editor.
To sign up to get future newsletters, go to: https://csp.sourcegear.com/preferences.aspx. This will require you to sign in with your email address to our Customer Service Portal, but once that dance is done, you will get fresh information pushed to you every three months or so.
Posted by Jeremy
Wed, 12 Dec 2007 19:07:00 GMT
One of the goals of the 4.1 development cycle was to begin the process of updating our web client to make it as cool as the web sites that some of our customers are creating as they use Vault and Fortress.
I’ve already blogged about the Tag Clouds, which brought along quite a bit of Dynamic HTML (yes, we’re about 8 years late to the DHTML party). The feature I want to highlight for this post is the new Web Diff page in the Source Control section of the web client.
You can view an example web diff here. Remember to log in using the guest1 through guest9 username with the username as the password. There are quite a few awesome features to talk about.
- Unified diff. This is the first place in Vault where we’ve shown a Unified Diff. All our other diff tools were concerned with migrating changes between the two versions, so unified was never a good option. Now that it’s in web diff, I love it. You can still load up the traditional side-by-side, but be prepared to scroll.
- Line Wrapping. This mode will wrap long lines, to reduce scrolling.
- Lines of context. Select the lines of context also. Please note that the three settings above are saved in a cookie, so that you can always get the view of differences that you want.
- Version Selection. You can also quickly select the versions of the file to diff from the dropdown.
- Transaction Details. To get the details for the transaction that created a particular version, you can click the Details link.
All of this was done by Jeff Hostetler, the same developer who brought us the wonderful SourceGear DiffMerge app, which is currently available free of charge.
With all of the changes modernizing the web client, we’re all excited about the release of .Net Framework 3.5, which includes built-in AJAX support. Expect an even richer web client experience in the future.
Posted by Jeremy
Tue, 04 Dec 2007 14:27:00 GMT
For those of you trying the Fortress 1.1 server beta, here’s something that we added that is pretty cool. We publicly stated in the release notes that 1.1 has support for Saved Queries in the web client. What we haven’t mentioned yet is that you can also use saved queries in the RSS feeds.
To set up an RSS feed for a Fortress server, subscribe to a URL that looks like this (please pardon the wrapped URL):
I’ve set up an example feed for the guest7 account over on fortressbeta.sourcegear.com. Here’s the URL if you would like to subscribe to it, to see how it works in your aggregator.
Sample RSS Feed
Posted by Jeremy
Mon, 26 Nov 2007 22:48:00 GMT
During the development of the 4.1 Vault release and the 1.1 release of Fortress, we’re trying to find new ways of keeping our customers informed about the changes that are coming. The Vault Blog the first step on improving our communication. The next step of that effort is more beta periods to give users a chance to offer input. We’re happy to announce the availability of the first of two planned beta periods for the 4.1/1.1 release. To ensure that more people can try this beta, the client portion of the beta will be able to connect to a 4.0/1.0 server. If you have questions, or just want to find out what people think of the beta, you can do so at our support forum. To see the web client portion of Fortress 1.1 in action, go to http://fortressbeta.sourcegear.com.
Here are some highlights of the new Beta:
- Tag Clouds. This new feature will help you to track work items by marking related bugs with keywords. For example, it would be possible to mark all bugs where words are misspelled with the “grammar” tag, regardless of which part of your system they occur. There are also views that help you look at a work item query and see at a glance, the relative weights of Assignees, Priorities, Categories, etc… For more details on this new feature, see: http://vaultblog.sourcegear.com/articles/2007/08/30/tag-clouds
- New Query Page / Saved Queries. The saved query feature, which was formerly only available in the Fortress Visual Studio client is now in the Web Client. Also, there is a new Work Item Query page.
- Paste and Edit images on the clipboard. This beta will introduce a new streamlined way to put images into work items. For this beta, this feature will only be available in the Fortress Eclipse plugin, but support for the Visual Studio plugin and the Windows GUI client will be added in the future.
Visual Studio Changes
- Visual Studio 2008 Support. This beta is the first release to support Visual Studio 2008.
- Legacy Options. Many users requested that some of the source control options that were supported in the 2003 compatible client be implemented in the 2005 client. The first two options supported are: Get Latest when a solution is opened and Check In when a solution is closed.
- Ant Tasks. This beta introduces support for Ant tasks.
- Java CLC. For users on non-Windows platforms, there is now a Java based command line client.
Posted by Jeremy
Thu, 25 Oct 2007 21:54:00 GMT
We’re very happy to announce that Vault 4.0.5 is released now. Thanks to everyone who downloaded the beta. 4.0.5 is the most significant maintenance release for 4.0, and we hope that all of our users will appreciate the hard work that went into it.
4.0.5 is finally the release where we support having bound projects in an unbound solution in the Visual Studio 2005 client, which is something that everyone’s been requesting since hours after the 4.0.0 release. You can get to this new functionality by using the File->Change Vault Bindings… menu item. The new Change Bindings dialog will immediately look somewhat familiar to anyone who was used to the old MSSCCI Change Source Control Bindings dialog.
The other big feature in the 4.0.5 Visual Studio 2005 client is the elimination of the need to perform two get operations when someone else has added files to a project. It’s a deceptively simple feature that turned out to be quite hard to get working.
As an aside, expect some announcement of the first of two scheduled 4.1 beta periods in the next month. We’re about to deploy the full UI for tag clouds on our internal dogfood server, and I’m very much looking forward to using tags to drill down into our bugs.
Posted by Jeremy
Thu, 11 Oct 2007 14:16:00 GMT
We’ve now released version 3.1 of SourceGear DiffMerge. The important changes since the beta are:
We now support the “mark the first file, then browse to a different folder, select a second file and diff it against the first” workflow that was requested in the beta period.
There was a crash reported when clicking in the window while the files were still loading.
You can get the 3.1 release at our DiffMerge downloads page.
Thanks for your continued support of our products, and giving us the feedback we need to make high-quality dev tools.
Posted by Jeremy
Tue, 09 Oct 2007 16:42:00 GMT
Vault 4.0.5 has been two months in the making, which makes it the largest maintenance release yet for 4.0. There are several new features that we are sure that users will appreciate. We’ve tested it thoroughly, but would appreciate any feedback from users on the new features that we’ve added. You can download the beta at: http://www.sourcegear.com/vault/downloads.html
The largest changes are to the Visual Studio 2005 client:
A new Change Bindings dialog, which will allow users to configure an unbound solution with bound projects. This also moves the online/offline and binding operations from the context menu.
The Double-Get fix, which means that no longer will users be required to perform two get operations to get files that have been added to a project or solution.
The bin directory should no longer be added to source control for web site projects.
For the full release notes of the beta, see http://www.sourcegear.com/vault/releases/4.0.5b.html
Posted by Jeremy
Mon, 24 Sep 2007 14:27:00 GMT
In the comments for the post on Tag Clouds, I mentioned one of my goals was to actually provide the “standard” list of tags we use internally. These are tags that we use to imply priority, so that everyone on the team can look at a bug, see which tags apply to it and immediately know what priority the bug should be. I should also reiterate that a bug which was assigned a lower priority because of a tag like Trivial or Grammar will still get fixed more quickly than some higher-priority bugs. Tags are a labeling mechanism that makes them easier to find.
- Blocker: This bug is preventing others within the company from fixing or testing on other items. The item has a time-critical context that supersedes the perceived priority.
- Data Corruption: Any error, whether GUI or API, where server data is or can be corrupted.
- Broken Beyond Repair: Product feature does not work. No workaround exists
- Server Crash: Server crash of any kind.
- Obvious Client Crash: Client crash that is both reproducible and frequent
- Legal: Errors in wording or use of copyrighted material that presents legal ramifications.
- First Impression: Issues occurring in the first hour of use that negatively affect sales.
- Broken Causing Pain: Product feature is impacted, but the existing workaround requires extra steps or is impractical.
- Odd Client Crash: Client crash that is either reproducible or frequent
- Performance: Performance issues that are common.
- Support Headache: Small or medium impact, but creates substantial confusion and high support load.
- Fairly Common: Particular aspect of subfeature not working as designed, and likely to be seen by several customers.
- Broken with Workaround: Product functionality is impacted, but a viable workaround exists.
- Embarrassing: Impact is small or negligible, but visibility presents poor company image.
- Broken on Goofy System: Usability not present on certain older systems or non-prevalent machine setups.
- Well Contained: Particular aspect of sub-feature not working as designed.
- Odd Performance: Performance issues due to large or odd setups.
- Not User Friendly: Incorrect error messages likely to produce some support load.
- Unlikely, but Severe: Infrequent order of steps causes serious error.
- Bug on Goofy System: Usability reduced on certain older systems or non-prevalent machines setups.
- Hand-Holding: Product functionality doesn’t match user expectations, needs better alerts or help.
- Grammar: Incorrect or awkward titles or wordings in dialogs.
- Trivial: Feature impact is small or negligible, and not embarrassing.
- Phase of the Moon: Infrequent set up steps causes small error.
It has benefited us to make the priority guidelines for feature separate from bugs. In fact there have been times when trying and failing to find the appropriate bug-tags to put on an incoming item has caused me to think “That’s no bug… That’s a feature request!”
- Blocker: This feature is preventing others within the company from fixing or testing on other items. The item has a time-critical context that supersedes the perceived priority.
- Very Popular: Many people would be positively and substantially impacted by this addition. We have so many requests for this; we need a really good reason why NOT to add it.
- Internal Consistency: This feature would allow different clients to work the same as their counterparts.
- Preventative: The program works in a reasonable manner, yet certain bizarre work habits or program interactions will cause problems. This feature will prevent those from occurring.
- Extra Steps: Not having the feature forces the user to stop and figure out how to do what he intended to do by navigating through extra steps
- Exceeds Expectations: This feature’s existence pleasantly surprises the user, creating customer loyalty.
- First Impression: Feature additions that positively impact the first hour of use and therefore raise sales.
- Administration: This feature helps the IT guys maintain Vault with less hassle.
- Worthy: Many people would be positively or substantially impacted by this addition.
- Graceful: Functionality is not significant, but visibility presents good company image.
- User Friendly: Better help or error messages likely to reduce customer annoyance or support load.
- Performance: Adding this feature will improve program speed.
- VSSConsistency: It needs to work like VSS does.
- Options: Users would like another way to manage his workflow.
- Useful: Small featurette provides utility for a subset of customers.
- Odd Configurations: Usability requested for certain odd program interactions, or unsupported systems.
- Diversion: It’s a reasonable request, but it doesn’t quite fit in with our company direction.
- Misguided: A user is asking for something that ultimately would be a poor choice.
- Behemoth: While this is a reasonable request, implementing it would take excessive work and have consequences that will spiral out of control in terms of bugs.