On Mon, 9 Nov 2009 07:53:44 -0800 (PST)
Patrick McNamara <[email protected]> wrote:
> Releases do not belong in your source repository.
In a CM-theoretic way you are right. But...
> In your "standard" CM/build/release environment, development
> builds are done on some frequency. Depending on your release
> process, either one of those development builds will be deemed
> "releasable", or the decision will be made to make a separate release
> build. The source that will go into the build will be denoted in some
> fashion and the release build done off that source. The release binaries
> will be denoted in the same fashion and placed in a release
> "repository". The release binary is traceable back to the appropriate
> source by its version/build number/some identifier that is part of the
> binary itself. This identifier aligns with the identifier used to
> select the source used to generate the binary.
... I don't worry about tracebility. We already have that in svn.
It might not be perfect, but it's more than just good enough.
> In this way, a binary release is always reproducible, just by knowing
> its release identifier. The tooling used to generate the binary is always
> an issue as it is required to be "archived" along with the release if you
> need exact and absolute reproducibility. If not, then the above is enough
> for most situations.
That's exactly what i'm worring about. We wont have the tools we have
today in a few years. And if we do not link source code and binary
in a strong way, we might lose the binaries ("who cares about these
old releases anyways?") and will not be able to reproduce them again.
> "Normal" CM tools generally use labels for identification in situations
> like this. Subversion of course doesn't support labels. They closest it
> comes is making a new tag. Not exactly the same thing, but perhaps
> sufficient.
It is. Although at some point, most people wish that svn would have
real tags. But i have yet to see one issue where tags are not enough.
Attila Kinali
--
Das Internet ist nichts für gute, sozial integrierte Menschen
-- Lukas Beeler
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
