SDC, Part 10: Creating a Release

by Tim Rutter 14. June 2010 09:52
In the last blog Kenji took a good look at some of the current and upcoming reporting systems inside PureCM. Today I'm going to take a closer look at Releases. What is a Release? A release is a snapshot of the code at a specific point in time. This gives you a permanent copy of your code at a specific point, which typically will remain read only. You can directly browse the content of a release and use it for internal/external/beta/etc builds or to send to your testers. Having a release gives you an easy way to tag points in your development and keep track of who is running which version o... [More]

Tags: , , , , ,

Best practices | Deployment | PureCM

SDC, Part 6: Working on a small work item: tasks

by Tim Rutter 28. May 2010 17:03
In this part of the SDC series we are focusing on a developers day to day life. Last time Lee looked at developer workspaces, now we are going to look at how tasks interact with and manage those workspaces. My Tasks We already introduced the concept of a task in my last blog looking from a managers point of view. To a developer a task represents  a small chunk of work that has been assigned to them to complete. These can be easily viewed from the 'My Tasks' area. As you can see the tasks in this view are broken down into three sections; 'Working', 'Assigned' and 'Group'. These divide... [More]

Tags: , ,

Agile | Best practices | PureCM

SDC, Part 3: Defining a work item hierarchy

by Tim Rutter 19. May 2010 19:37
  SDC part 2 looked at managing your project structure using versions and releases. This blog is an introduction to creating, organising and scheduling work between your releases.   Specify your Work We need a way of recording work that needs to be done. Using PureCM projects this is done using both Tasks and Features. Tasks A task is the basic building block of project workflow. Ideally it should be a small self contained item that will be submitted as one changeset. Large pieces of work should be broken down into the smallest chunks possible. Code changes you make will be rec... [More]

Tags: , , ,

Agile | Best practices | PureCM

The Old Friend Visual Studio

by Tim Rutter 21. August 2009 11:44
Introducing the exciting new PureCM Visual Studio Plug-in. [More]

Tags:

Plug-ins | PureCM | Workspace

PureCM Deployment Service

by Tim Rutter 20. January 2009 16:39
This seems like a good time to tell you of a new feature going to be released early this year, the PureCM Deployment Service. We are always committed to not just looking after your files but also making your daily work flow easier. The deployment service will be a new stand alone service which you can run to automatically transfer files as changes are made over FTP/SFTP to a server of your choice. Why use it? This has been designed to enable you to keep your files up to date on a remote server without having to install PureCM on that machine. One practical example of this is keep... [More]

Tags: ,

Plug-ins | PureCM | Deployment

Better Merging - Part 1

by Tim Rutter 7. November 2008 10:09
One of the great strengths of PureCM has always been it's support for parallel development. PureCM's merge functionality allows you to keep track of your changesets and which streams they have been submitted against while making it easy for you to merge these changes into other streams as desired. Now we are looking at making merging even more powerful and simple, but let's first take a look at how merging works today. Merging Today The original merge process required you to own a workspace for the stream you are merging into. This gives you a number of benefits such ... [More]

Tags: , , ,

Agile | Parallel development

Powered by BlogEngine.NET 1.6.0.0