| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Page <dpage(at)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20 |
| Date: | 2007-09-12 14:59:55 |
| Message-ID: | 22516.1189609195@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Page <dpage(at)postgresql(dot)org> writes:
> Tom Lane wrote:
>> Peter usually does it --- in theory any committer could, but he actually
>> knows what to do and the rest of us would have to study ;-)
> Study or figure it out? If it hasn't already been it should be
> documented as part of the release process.
Well, RELEASE_CHANGES has
* Translation updates
Translations are kept in the project "pgtranslation" on PgFoundry.
1. Check out the messages module (of the right branch).
2. Check out the admin module.
3. Run "sh .../admin/cp-po .../messages .../pgsql
4. Commit.
but it's not real clear (to me) which is "the right branch" and what
the ...s signify. It's not a big knowledge gap but I have other things
to worry about ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-12 15:54:14 | Re: A small mistake in the initial latestCompletedXid idea |
| Previous Message | Tom Lane | 2007-09-12 14:48:59 | Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20 |