granicus.if.org Git - postgresql/blob - doc/src/sgml/release.sgml

   1 <!-- doc/src/sgml/release.sgml -->
   2 <!--
   3
   4 Typical markup:
   5
   6 &<>                             use & escapes
   7 PostgreSQL                      <productname>
   8 postgresql.conf, pg_hba.conf,
   9         recovery.conf           <filename>
  10 [A-Z][A-Z_ ]+[A-Z_]             <command>, <literal>, <envar>, <acronym>
  11 [A-Za-z_][A-Za-z0-9_]+()        <function>
  12 \-\-?[A-Za-z_]+[-A-Za-z_]*      <option> (use backslashes to avoid SGML markup)
  13 [A-Za-z_]+/[A-Za-z_]+           <filename>
  14 psql                            <application>
  15 pg_[A-Za-z0-9_]+                <application>, <structname>
  16 [A-Z][A-Z][A-Z_ ]*              <type>
  17 [a-z]+_[a-z_]+                  <varname>, <structfield>
  18                                 <systemitem class="osname">
  19
  20 non-ASCII characters            find using grep -P '[\x80-\xFF]'
  21                                 convert to HTML4 named entity (&) escapes
  22
  23         official:      http://www.w3.org/TR/html4/sgml/entities.html
  24         one page:      http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
  25         other lists:   http://www.zipcon.net/~swhite/docs/computers/browsers/entities.html
  26                        http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
  27                        http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
  28
  29         we cannot use UTF8 because SGML Docbook does not support it
  30
  31         do not use numeric _UTF_ numeric character escapes (&#nnn;),
  32         we can only use Latin1
  33
  34         Example: Alvaro Herrera is &Aacute;lvaro Herrera
  35
  36 wrap long lines
  37
  38 For new features, add links to the documentation sections.
  39
  40 -->
  41
  42 <appendix id="release">
  43  <title>Release Notes</title>
  44
  45   <para>
  46    The release notes contain the significant changes in each
  47    <productname>PostgreSQL</> release, with major features and migration
  48    issues listed at the top.  The release notes do not contain changes
  49    that affect only a few users or changes that are internal and therefore not
  50    user-visible.  For example, the optimizer is improved in almost every
  51    release, but the improvements are usually observed by users as simply
  52    faster queries.
  53   </para>
  54
  55   <para>
  56    A complete list of changes for each release can be obtained by
  57    viewing the <link linkend="git">Git</link> logs for each release.
  58    The <ulink
  59    url="https://archives.postgresql.org/pgsql-committers/"><literal>pgsql-committers</literal>
  60    email list</ulink> records all source code changes as well.  There is also
  61    a <ulink url="https://git.postgresql.org/gitweb?p=postgresql.git;a=summary">web
  62    interface</ulink> that shows changes to specific files.
  63   </para>
  64
  65   <para>
  66    The name appearing next to each item represents the major developer for
  67    that item.  Of course all changes involve community discussion and patch
  68    review, so each item is truly a community effort.
  69   </para>
  70
  71 <!--
  72   To add a new major-release series, add an entry here and in filelist.sgml.
  73
  74   The reason for splitting the release notes this way is so that appropriate
  75   subsets can easily be copied into back branches.
  76 -->
  77 &release-10;
  78 &release-9.6;
  79 &release-9.5;
  80 &release-9.4;
  81 &release-9.3;
  82 &release-9.2;
  83 &release-9.1;
  84 &release-9.0;
  85 &release-8.4;
  86 &release-8.3;
  87 &release-8.2;
  88 &release-8.1;
  89 &release-8.0;
  90 &release-7.4;
  91 &release-old;
  92
  93 </appendix>