Category: General Geekery

  • November 04, 2013

    What are we using this time?

    In the first part of this article I explained why to have a report of all changes not related to an approved review for a given branch in Perforce. Now it is time to implement such a report and we need to get our tooling sorted. For the task at hand we need to query Perforce and Swarm data, and although you could use almost anything, I’m picking Groovy as the scripting language.

    Posted In:
  • October 23, 2013

    The functionality described in this blog entry is "undocumented", meaning that it is in some respects a work in progress, is subject to change in future releases, and should be treated with a bit more caution than "documented" functionality. With that disclaimer out of the way, let's take a look at how you can now version the character sets for individual Unicode files!

  • October 14, 2013

    The Balance of Freedom and Control

    A lot of Perforce users really like what they see when I show them Swarm. Almost everybody involved in Software Development wants to do some kind of code review, however, there are discussions on how liberal or how strict a review process should be. In every development process the pendulum swings more towards freedom or more towards control.

    Posted In:
  • October 10, 2013

    In the days before streams, it was commonly accepted that if files had different names in different branches, you would need to set up a branch spec that mapped one set of file names to the other if you wanted to integrate changes between those branches. When we began developing streams functionality, we knew we would need to provide another way to handle refactoring within streams, since the branch view used to merge changes between a stream and its parent is dynamically generated and is supposed to be a relatively simple function of the paths specified for each stream – hence we came up with a system for matching different filename variants within a source and target to each other and setting up resolves between them.

  • September 16, 2013

    As a Perforce user, you have a voice that can shape the future of our products. And we are listening closely. Collecting feedback from our customers to understand their wants and needs is always an important step when defining product roadmaps and prioritizing upcoming features.

  • September 03, 2013

    For the past several months, I've been on loan to the Git Fusion QA team.  It's been interesting to see the intersection of these two very different systems.  One thing our development team has done is extended some of the git commands to return Perforce and Git Fusion specific information.  Here's a page from our user manual:

    Posted In:

Pages