How do you handle build & release management?
-
Hi, Lately I've been trying to find a more structured way to handle how we build software and release different versions of it. I've been playing with Visual Build Professional which so far seems to be able to do automated builds, with integration of source control systems and making installers, but now I'm looking for a way to keep track of which version of the software was released when and to who (preferbly with integration of source control tagging, uploading to website, burning cd's etc) but I cannot find any software that does this, apart from some high-end IBM or Rational solutions (which I haven't even asked a price for - if you have to ask, you can't afford it, is my motto). Anyway, I was wondering how other developers handle this. Do you have an Excel sheet where you keep track of which beta/released version you send out to who and when or do you have something more advanced?
-
Hi, Lately I've been trying to find a more structured way to handle how we build software and release different versions of it. I've been playing with Visual Build Professional which so far seems to be able to do automated builds, with integration of source control systems and making installers, but now I'm looking for a way to keep track of which version of the software was released when and to who (preferbly with integration of source control tagging, uploading to website, burning cd's etc) but I cannot find any software that does this, apart from some high-end IBM or Rational solutions (which I haven't even asked a price for - if you have to ask, you can't afford it, is my motto). Anyway, I was wondering how other developers handle this. Do you have an Excel sheet where you keep track of which beta/released version you send out to who and when or do you have something more advanced?
roel_ wrote:
Do you have an Excel sheet where you keep track of which beta/released version you send out
In our case we do it off of version number. All test releases whether they leave my desk or not are +0.0.0.1 version number. When we have tested and believe we are ready to release. If we release to any customer +0.0.1 version number. IIf a full, wide distribution, give to everyone, we're all fine and hopeful here +0.1 release. And of course Large rewrites/redesigns are +1. Release numbers are recorded in the source code. It's long though. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) -- modified at 13:09 Thursday 3rd November, 2005
-
roel_ wrote:
Do you have an Excel sheet where you keep track of which beta/released version you send out
In our case we do it off of version number. All test releases whether they leave my desk or not are +0.0.0.1 version number. When we have tested and believe we are ready to release. If we release to any customer +0.0.1 version number. IIf a full, wide distribution, give to everyone, we're all fine and hopeful here +0.1 release. And of course Large rewrites/redesigns are +1. Release numbers are recorded in the source code. It's long though. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) -- modified at 13:09 Thursday 3rd November, 2005
Jeffry J. Brickley wrote:
I full, wide distribution, give to everyone, we're all fine and hopeful here +0.1 release
:~ Regards Senthil _____________________________ My Blog | My Articles | WinMacro
-
Jeffry J. Brickley wrote:
I full, wide distribution, give to everyone, we're all fine and hopeful here +0.1 release
:~ Regards Senthil _____________________________ My Blog | My Articles | WinMacro
yeah, compiling, making changes, preparing for a presentation tomorrow, and tracking my blood pressure then I had to come here.... I wrote it too fast, it's corrected at least better. Of course now my blood-pressure won't register... hmmm I wonder if I topped the machine.... _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Hi, Lately I've been trying to find a more structured way to handle how we build software and release different versions of it. I've been playing with Visual Build Professional which so far seems to be able to do automated builds, with integration of source control systems and making installers, but now I'm looking for a way to keep track of which version of the software was released when and to who (preferbly with integration of source control tagging, uploading to website, burning cd's etc) but I cannot find any software that does this, apart from some high-end IBM or Rational solutions (which I haven't even asked a price for - if you have to ask, you can't afford it, is my motto). Anyway, I was wondering how other developers handle this. Do you have an Excel sheet where you keep track of which beta/released version you send out to who and when or do you have something more advanced?
a really dirty, hairy batch file builds "VSS TO binaries", another less hairy but quicker breaking batch file (thanks InstallSh*t) builds install resources to disk & download image. [edit] Versioning is quite complicated: the first two numbers indicate the version of the module (which may differe for one release), the 3rd indicates the public release, 4th digit != 0 are in-house builds mostly (or "can't you just send Jeff that DLL?"-"well..." releases) Release tree information is available in an excel sheet since recently (was an hard-to maintain excel table before)
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen -- modified at 19:16 Thursday 3rd November, 2005