Version Control
Articles
Taking the Complexity out of Release Management CM is complex enough without having to worry about managing releases! Release management, however, isn't just part of CM, it should be driving your CM solution. Release management deals with defining, using and managing the set of deliverables (the Build), for all of your customers. This includes the creation of records to subsequently identify release contents, the creation of variant builds, patch releases, incremental releases, and the support of parallel streams of releases (older product releases, current release(s) and future releases). It also deals with the ability to know what’s in a release and to compare one release (e.g. one being sent to a customer) to another (e.g. the one the customer currently has so that the customer is well aware of the changes being made to his environment and how they match up against his requirements). In an end-to-end product management environment, release management spans the entire spectrum from requirements management through to product retirement. |
||
ABCs of BPD (Build, Package, and Deploy) Many in the software engineering world consider build, package, and deploy the core areas of configuration management (CM). To highlight this, many CM jobs are titled “build engineer” or “release engineer” with responsibilities that focus on the tasks of building, packaging, and deploying releases. |
||
Don't Become Hostage to Development Process Suites Not many years ago, there seemed to be an increased demand that software development tools become better integrated. Now, it is expected that all software process tools from a single software house are tightly integrated. I started evaluating software process suites, and started promoting them to our development teams. |
David Baird
December 5, 2005 |
|
Makefile Optimization: $(shell) and := go Together Ask Mr. Make discusses Makefile optimization: ow $(shell) and := go together. |
||
Making Incremental Integration Work for You Recent CM Crossroads posts have suggested that a branch-per-change branching strategy is good because it gives you the ability to maintain a stable "main" trunk, while integrating a change at a time if you want. As Joseph Reedick put it in one of his responses: |
||
Multi-Site Servers - Get it Right I've been involved in database development for 30 years and CM development for over a quarter century. I'm confused. Why is it so difficult to get working multi-site solutions? The specification is clear, to start off anyway: I want to see the same thing whether my client is connected to the London server or the New York server. |
||
The Importance of Software Builds: Building Earnestly Building your application is key to a successful, repeatable, development process. A reproducible build that works at all levels allows you to proceed with confidence and be more agile. Yet many organizations (agile and not) leave the build process to chance, even though all can benefit, regardless of their method. |
||
Aircraft Carrier Called the "CM" In the past, I had a window view of the Boston Harbor from my office. I could see boats coming in an out, including numerous tour boats, whale watch boats, and sail boats. Occasionally, I got the chance to see the large ships including the tankers, battleships, tall ships (e.g., elegant large sailing ships), and the rare site of an aircraft carrier. The aircraft carrier is a floating runway for jets. Imagine the infrastructure needed to get those incredibly fast jets ready and flying.
|
||
Requirements Driven Development: A Stream-Based WBS Approach Requirements are a must have. Or should have. Maybe a want. OK, maybe not really requirements. When it comes down to it, you need to understand why you're building what you're building in sufficient detail so that you will know if what you built does the job. You also need full traceability to show that you have met the requirements. Developers work to a set of requirements, but these are not the same as the product requirements, which are again different from the customers' requirements. And what about ad hoc requests? Where do they fit in? |
||
Integrating an SCM Tool with a Java Development Platform: The IDE has emerged as the de-facto development tool in many Java shops. As the Java IDE evolved, team support became an important aspect of the tool and plays a prominent role in the popular Java development environment, IBM WebSphere Studio Application Developer 5.0 (WSAD). The clean design of the SCM interface to WSAD means configuration managers do not need to craft a custom solution to integrate their organization’s SCM tool with the IDE. |
Michael Sayko
November 30, 2005 |
Pages
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |