[Gllug] Practical release and deployment - how?

[Sean Burlington]

Ziya Suzen wrote:
> Hi there
> 
> What do you use (as tools or practices) for releasing and deploying
> your code (internal to the company)?
> 

I've been very happy using eclipse, with the subclipse plugin,
svn-commit-hooks and trac ( http://trac.edgewall.org/ )

This gives me a high level of integrated control - I can browse and tag
my svn repository from within my development environment, mark tickets
as closed in commit messages - and have lots of cross references between
tickets, tags, check-ins, and documentation.

My projects are web based - I always create directories named by the
version and symlink this to public_html. In the event that I then
discover a bug after launch it is at least easy to roll back (lessening
the red face syndrome).

I tend to script most of this process once a project is more or less stable.

I have created RPM/deb packages where I want to use a newer version of a
package that is enmeshed in the dependency hierarchy and found this to
be worthwhile.

-- 

Sean
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug