On 29/03/06, Lakshman Srilakshmanan
<lakshman.srilakshmanan@tradingpost.com.au> wrote:
> Hi James,
>
> Using a version control system to determine/manage what should be
> released to a customer (release control) may not necessarily be the
> right way of doing it.
>
> I use a release script (ie ant) to create a release directory and
> prepare it for release to
> the customer. This script is modified for every release and versioned
> controlled.
>
> This ensures that there is little room for error. Every time you
> checkout a "Release Tag", you are able to reproduce the release package
> as it appeared in the original release.
>
> Thanks
> Lakshman
>
To put this in context, the feature I describe is in a package called
ClearCase. http://www-306.ibm.com/software/awdtools/clearcase/
I am trying to get svn to mirror some of the features of ClearCase,
and this "views" feature is a way to have a view of a potential
release as it is nearing release, but still changing.
I could add this feature to svn, but I don't really want to try unless
svn developers think it is a good idea.
As for release control, release control is just a "process", with
things like svn just being tools in that process. If a tweek to svn
could make the process more efficient, then I think it would be worth
doing. I believe that my suggestion of labels and views would result
in you not needed any "release scripts", so surely that would make
things more efficient for you also.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 29 11:29:15 2006