[Gllug] Practical release and deployment - how?

[Bruce Richardson]

On Wed, Nov 07, 2007 at 02:07:07PM +0000, Richard wrote:
> 
> In other words you're not using SVN for anything other than to track
> the history of your releases.
> 
> You really should start to take a look at branches as soon as
> possible.
> 
> Decide on a version numbering scheme (it could be as simple as "next
> version will 3.1").  Develop along the HEAD, checking in all changes
> as you go along.  When you are happy with the result, create a 3.1
> branch.  This branch is what you should check out and release.  Any


You only have half the picture there; you've left out tags.  Yes, use
branches to separate each scheduled release, that's a good idea, but
what you should release is a tag.  *That* is what you should check out
and release.  Here is why:

> vital bugfixes can also be checked in or merged into the 3.1 branch
> and released.  Normal development continues along HEAD.

But now you have destroyed your record of what you actually released in
the first place.  Sure, you had previously checked out a copy, but where
is your guarantee of the integrity of that?  If you tag the branch and
release the tag, you have a record in your repository of exactly what
you released.  Since tags (and branches) are so cheap in subversion, why
not take this level of care?

-- 
Bruce

Hierophant: someone who remembers, when you are on the way down,
everything you did to them on the way up.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: Digital signature
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20071108/cf0b7697/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug