[Anthill-pro] Release builds

[Peter Steele]

[This is essentially a repost; there were subscription issues with my email address so I missed any replies that may have been posted for my original message.]

 

What model does Anthill recommend for dealing with release candidate builds? I’ve seen different approaches used at different companies I’ve worked for in the past. One company used a “promote” process, where when they would decide that a certain build was going to be the official release, they’d modify certain resource files in the build directory to reflect the version number and then force a relink of the binaries to create the new release artifacts. Another company took a completely different approach, where they would turn on a “release candidate” flag in the build system and from that point on the builds produced had official release version strings compiled into the binaries and other special behavior needed only for release builds.

 

We’re a new company and are going to have to pick a model some time soon. I know Anthill is flexible enough to support either of these approaches, and anything else we might go with instead. Is there a recommended model though that we should follow?

 


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.8/1287 - Release Date: 2/19/2008 10:55 AM
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080219/b1222ff8/attachment.htm