Robert Haas on 13 Feb 2008 17:51:31 -0800


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: release management

  • From: "Robert Haas" <robertmhaas@gmail.com>
  • To: phl@lists.pm.org
  • Subject: Re: release management
  • Date: Wed, 13 Feb 2008 20:51:10 -0500
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=TurVlJMN8tLsJ9sAMWcjDxDiIN5AeIZxfFk5RcJ8YFQ=; b=DPXaKDAvj2WHMEPCM756j0mY2FaT9PnsrGzsfN8KkEG0KWm+QVgiwC3S+1L3l1Cezr6J1bji4ZJVBqvOU7+Mjg6IQWeF5ZTf/vXo++N5OGgJ5hSRNRAeRfnGVgzos/TFezwnmjV2wLt/+Do/LxF5vAkQbTY+AUmUJVKv0iBMOUg=
  • Reply-to: phl@lists.pm.org
  • Sender: owner-phl@lists.pm.org

I guess it depends on where you're trying to release *TO*.  On one
project I work on, I tag each release and then just export out that
branch on the production server - this of course only works if your
whole project is going in one directory that has nothing else in it.
Another option if on Linux or UNIX is to use your operating system's
package management system (e.g. RPM).

I do a lot of web development so I find that the hardest part is
actually to manage the database schema.  You need to make sure that
the schema changes on production exactly match what you did on dev.
I've written some scripts to help me do this, basically by having a
database table that keeps track of which DDL files have been run on
each machine, and a script that executes all the un-run files (except
certain files are set up to always run, mostly CREATE OR REPLACE VIEW
since it's idempotent).

...Robert

On Feb 11, 2008 8:57 AM, Nguon Hao Ching <spiderboy@pobox.com> wrote:
> How do you guys manage non-Java releases (with Subversion)?
>
> Googling doesn't seem to help.  Everyone seems to be obsessed
> with continuous integration or Ant-based J2EE development.
>
> I'm just looking to automate release packaging.
>
> I'm wondering if I should just roll my own, or if there's
> already a preexisting semi-standard system out there.
>
> Thanks.
>
> -Hao
>
>
> -
> **Majordomo list services provided by PANIX <URL:http://www.panix.com>**
> **To Unsubscribe, send "unsubscribe phl" to majordomo@lists.pm.org**
>
-
**Majordomo list services provided by PANIX <URL:http://www.panix.com>**
**To Unsubscribe, send "unsubscribe phl" to majordomo@lists.pm.org**