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    <filename>
   9 \<[A-Z][A-Z_ ]+[A-Z_]\>         <command>, <literal>, <envar>, <acronym>
  10 \<[A-Za-z_][A-Za-z0-9_]+()      <function>
  11 \-\-?[A-Za-z_]+[-A-Za-z_]*      <option> (use backslashes to avoid SGML markup)
  12 \<[A-Za-z_]+/[A-Za-z_]+\>       <filename>
  13 psql                            <application>
  14 pg_[A-Za-z0-9_]+                <application>, <structname>
  15 \<[A-Z][A-Z][A-Z_ ]*\>          <type>
  16 \<[a-z]+_[a-z_]+\>              <varname>, <structfield>
  17                                 <systemitem class="osname">
  18
  19 wrap long lines
  20
  21 For new features, add links to the documentation sections.
  22
  23 -->
  24
  25 <appendix id="release">
  26  <title>Release Notes</title>
  27
  28   <para>
  29    The release notes contain the significant changes in each
  30    <productname>PostgreSQL</productname> release, with major features and migration
  31    issues listed at the top.  The release notes do not contain changes
  32    that affect only a few users or changes that are internal and therefore not
  33    user-visible.  For example, the optimizer is improved in almost every
  34    release, but the improvements are usually observed by users as simply
  35    faster queries.
  36   </para>
  37
  38   <para>
  39    A complete list of changes for each release can be obtained by
  40    viewing the <link linkend="git">Git</link> logs for each release.
  41    The <ulink
  42    url="https://www.postgresql.org/list/pgsql-committers/"><literal>pgsql-committers</literal>
  43    email list</ulink> records all source code changes as well.  There is also
  44    a <ulink url="https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary">web
  45    interface</ulink> that shows changes to specific files.
  46   </para>
  47
  48   <para>
  49    The name appearing next to each item represents the major developer for
  50    that item.  Of course all changes involve community discussion and patch
  51    review, so each item is truly a community effort.
  52   </para>
  53
  54   <para id="release-commit-links">
  55    Section markers (&sect;) in the release notes link to <ulink
  56    url="https://git.postgresql.org/gitweb/?p=postgresql.git"><application>gitweb</application></ulink>
  57    pages which show the primary <application>git</application> commit
  58    messages and source tree changes responsible for the release note item.
  59    There might be additional <application>git</application> commits which
  60    are not shown.
  61   </para>
  62
  63 <!--
  64   When beginning a new major-release series, create a new release-NN.sgml
  65   file, removing the previous one, and change the &-reference here.
  66   Don't forget to update filelist.sgml.
  67
  68   The reason for keeping each branch's release notes in a differently-named
  69   file is to reduce confusion when preparing minor-release updates.
  70   All the active branches have to be edited concurrently when doing that.
  71 -->
  72
  73 &release-18;
  74
  75  <sect1 id="release-prior">
  76   <title>Prior Releases</title>
  77
  78   <para>
  79    Release notes for prior release branches can be found at
  80    <ulink url="https://www.postgresql.org/docs/release/"><literal>https://www.postgresql.org/docs/release/</literal></ulink>
  81   </para>
  82  </sect1>
  83
  84 </appendix>