From: Jim C. Nasby <jnasby@pervasive.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Davidson, Robert <robdavid@amazon.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Nightly builds
Date: Fri, 24 Mar 2006 08:45:29 -0600
Message-ID: <20060324144529.GO90527@pervasive.com> (raw)
In-Reply-To: <442402FB.2050102@dunslane.net>
References: <8333C841129E074E9F83FC80676BA76E405230@exchg-sea3-03.ant.amazon.com>
<20060324132144.GI90527@pervasive.com>
<442402FB.2050102@dunslane.net>
On Fri, Mar 24, 2006 at 09:32:27AM -0500, Andrew Dunstan wrote:
> Jim C. Nasby wrote:
>
> >On Thu, Mar 23, 2006 at 05:30:28AM -0800, Davidson, Robert wrote:
> >
> >
> >>How amazing is that? I call it a night and come back to find that a bug
> >>has been identified and patched while I sleep.
> >>
> >>When will it appear in the binaries (I see that the release version is
> >>still 8.1.3)? I thought about trying to compile from source, but after
> >>looking at the mingw page was too intimidated by figuring out what to
> >>download to try compiling source.
> >>
> >>
> >
> >We generally don't worry about point releases too much unless there's a
> >pretty serious bug, so it'll probably take a while.
> >
> >Unfortunately I don't know of anyone building nightly binaries. This is
> >something we should think about doing, especially for windows...
> >
> >
>
> What for? The only binaries we should be letting out are for declared
> releases. If the bug is serious enough to warrant cutting a generally
> distributed binary for, it's worth making a release for, IMNSHO. The
> Windows packaging team usually follow up a release with a package very
> quickly indeed.
In this case, my guess is that this bugfix isn't important enough to
push a release. If there was a nightly build, the bug reporter could use
that for development until an official release came out.
The only reason I even suggested this is because setting up a windows
build environment is substantially more complicated than building on
unix. If he was on unix, he could easily just cvs up on the appropriate
branch and build it himself.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jnasby@pervasive.com, andrew@dunslane.net, robdavid@amazon.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Nightly builds
In-Reply-To: <20060324144529.GO90527@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox