1 #######################################################################################
2 # Copyright ETSI Contributors and Others.
4 # Licensed under the Apache License, Version 2.0 (the "License");
5 # you may not use this file except in compliance with the License.
6 # You may obtain a copy of the License at
8 # http://www.apache.org/licenses/LICENSE-2.0
10 # Unless required by applicable law or agreed to in writing, software
11 # distributed under the License is distributed on an "AS IS" BASIS,
12 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
14 # See the License for the specific language governing permissions and
15 # limitations under the License.
16 #######################################################################################
19 Replace this text with content to appear at the top of the section for this
20 release. All of the prelude content is merged together and then rendered
21 separately from the items listed in other parts of the file, so the text
22 needs to be worded so that both the prelude and the other items make sense
23 when read independently. This may mean repeating some details. Not every
24 release note requires a prelude. Usually only notes describing major
25 features or adding release theme details should have a prelude.
28 List new features here, or remove this section. All of the list items in
29 this section are combined when the release notes are rendered, so the text
30 needs to be worded so that it does not depend on any information only
31 available in another section, such as the prelude. This may mean repeating
35 List known issues here, or remove this section. All of the list items in
36 this section are combined when the release notes are rendered, so the text
37 needs to be worded so that it does not depend on any information only
38 available in another section, such as the prelude. This may mean repeating
42 List upgrade notes here, or remove this section. All of the list items in
43 this section are combined when the release notes are rendered, so the text
44 needs to be worded so that it does not depend on any information only
45 available in another section, such as the prelude. This may mean repeating
49 List deprecations notes here, or remove this section. All of the list
50 items in this section are combined when the release notes are rendered, so
51 the text needs to be worded so that it does not depend on any information
52 only available in another section, such as the prelude. This may mean
53 repeating some details.
56 Add critical notes here, or remove this section. All of the list items in
57 this section are combined when the release notes are rendered, so the text
58 needs to be worded so that it does not depend on any information only
59 available in another section, such as the prelude. This may mean repeating
63 Add security notes here, or remove this section. All of the list items in
64 this section are combined when the release notes are rendered, so the text
65 needs to be worded so that it does not depend on any information only
66 available in another section, such as the prelude. This may mean repeating
70 Add normal bug fixes here, or remove this section. All of the list items
71 in this section are combined when the release notes are rendered, so the
72 text needs to be worded so that it does not depend on any information only
73 available in another section, such as the prelude. This may mean repeating
77 Add other notes here, or remove this section. All of the list items in
78 this section are combined when the release notes are rendered, so the text
79 needs to be worded so that it does not depend on any information only
80 available in another section, such as the prelude. This may mean repeating