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