1 <!-- doc/src/sgml/release.sgml -->
7 PostgreSQL <productname>
8 postgresql.conf, pg_hba.conf,
9 recovery.conf <filename>
10 [A-Z][A-Z_ ]+[A-Z_] <command>, <literal>, <envar>
11 [A-Za-z_][A-Za-z0-9_]+() <function>
13 [A-Za-z_]/[A-Za-z_]+ <filename>
15 pg_[A-Za-z0-9_]+ <application>, <structname>
16 [A-Z][A-Z][A-Z_ ]* <type>, <varname>
18 non-ASCII characters convert to HTML4 entity (&) escapes
20 official: http://www.w3.org/TR/html4/sgml/entities.html
21 one page: http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
22 other lists: http://www.zipcon.net/~swhite/docs/computers/browsers/entities.html
23 http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
24 http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
26 we cannot use UTF8 because SGML Docbook
28 http://www.pemberley.com/janeinfo/latin1.html#latexta
30 Alvaro Herrera is Álvaro Herrera
34 For new features, add links to the documentation sections. Use </link>
35 not just </> so that generate_history.pl can remove it, so HISTORY.html
36 can be created without links to the main documentation. Don't use <xref>.
40 <appendix id="release">
41 <title>Release Notes</title>
44 The release notes contain the significant changes in each
45 <productname>PostgreSQL</> release, with major features and migration
46 issues listed at the top. The release notes do not contain changes
47 that affect only a few users or changes that are internal and therefore not
48 user-visible. For example, the optimizer is improved in almost every
49 release, but the improvements are usually observed by users as simply
54 A complete list of changes for each release can be obtained by
55 viewing the <link linkend="git">Git</link> logs for each release.
57 url="http://archives.postgresql.org/pgsql-committers/"><literal>pgsql-committers</literal>
58 email list</ulink> records all source code changes as well. There is also
59 a <ulink url="http://git.postgresql.org/gitweb?p=postgresql.git;a=summary">web
60 interface</ulink> that shows changes to specific files.
64 The name appearing next to each item represents the major developer for
65 that item. Of course all changes involve community discussion and patch
66 review, so each item is truly a community effort.
70 To add a new major-release series, add an entry here and in filelist.sgml.
71 Follow the naming convention, or you'll confuse generate_history.pl.
73 The reason for splitting the release notes this way is so that appropriate
74 subsets can easily be copied into back branches.