| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Devrim GÜNDÜZ <devrim(at)commandprompt(dot)com> |
| Subject: | Re: How do we create the releases? |
| Date: | 2007-06-07 11:15:25 |
| Message-ID: | 20070607111525.GG28966@svr2.hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 07, 2007 at 01:12:06PM +0200, Peter Eisentraut wrote:
> Magnus Hagander wrote:
> > Is this script in CVS somewhere? I know it's not in the main backend
> > repo.
>
> Most of what these scripts have done in the past has been systematized
> and folded into the "make dist" target in the mean time, and AFAICT, we
> could integrate the documentation preparation as well, now that it
> works automatically in a reliable fashion. That would reduce the
> answer to the original question to something like
>
> ./configure
> make dist[check]
If we can do that, that makes it even better. But is it something we can
reasonably backpatch? Otherwise we still need both documentation and
scripts to deal with back branches.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GÜNDÜZ | 2007-06-07 11:22:22 | Re: How do we create the releases? |
| Previous Message | Peter Eisentraut | 2007-06-07 11:12:06 | Re: How do we create the releases? |