Release Management versions control?
We recently experienced a deployment issue where it turned out that the version objects were not in sync in one of the environments.
How can rotating release managers improve a project’s velocity and stability?
The Wikipedia article on Parrot VM includes this unreferenced claim:
Branching and CI Builds with Agile
We follow many agile processes, including automated tests, continuous integration, sprint reviews, etc… We’re currently having a debate about how often we should branch release builds.
Must all new features go through betatest?
Obviously, small usability fixes and bugfixes go directly into the stable product. What about small new features? Can you afford to just release them after internal testing, or do they have to be betatested by customers first?
Complex Release Vehicle Management
I’m looking into improving our build and release system. We are a .Net/Windows shop, and I don’t see any really good tools for Windows for generating the files that are to be dropped in patch or hotfix. We are currently using TFSBuild 2010 with Windows Workflows for our continuous integration builds as well as our daily full build which includes an Installshield package for deployment.
How do I know if a particular build has a particular version control change in it?
Let’s say I have a build. I need to know if a particular changelist/commit is present in that build.
How should we draw the release burndown chart?
I have been in various Agile projects and seen many release burndown chart styles. Most of them were handled manually since somehow all the tools that I have run across don’t produce really useful burndown charts.
Shorter release cycle with DVCS
Does the choice of using a DVCS over a CVCS actually make for shorter release cycles? If so, what makes software release cycles shorter and what are the arguments for this?
How do I avoid feature creep on a solo project?
So I have a program I’m worked on back in 2011 and all through 2012, but the last release was in December of 2011. I’ve been actively working on it, but feature creep lured its ugly head and now it is filled with tons on unfinished features.
Feasibility of continuous delivery with a mixture of development platforms
What are the major obstacles (and potential solutions, if known) for implementing “continuous delivery” software development when an application relies on varied programming languages or modules… especially when the same version-control and/or automated testing packages do not exist for those disparate platforms?