Get 'mvn clean site' to work.
[commons-testing.git] / src / changes / changes.xml
1 <?xml version="1.0"?>
2 <!--
3 Licensed to the Apache Software Foundation (ASF) under one or more
4 contributor license agreements. See the NOTICE file distributed with
5 this work for additional information regarding copyright ownership.
6 The ASF licenses this file to You under the Apache License, Version 2.0
7 (the "License"); you may not use this file except in compliance with
8 the License. You may obtain a copy of the License at
9
10 http://www.apache.org/licenses/LICENSE-2.0
11
12 Unless required by applicable law or agreed to in writing, software
13 distributed under the License is distributed on an "AS IS" BASIS,
14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15 See the License for the specific language governing permissions and
16 limitations under the License.
17 -->
18
19 <!--
20 This file is also used by the maven-changes-plugin to generate the release notes.
21 Useful ways of finding items to add to this file are:
22
23 1. Add items when you fix a bug or add a feature (this makes the
24 release process easy :-).
25
26 2. Do a JIRA search for tickets closed since the previous release.
27
28 3. Use the report generated by the maven-changelog-plugin to see all
29 SVN commits. TBA how to use this with SVN.
30
31 To generate the release notes from this file:
32
33 mvn changes:announcement-generate -Prelease-notes [-Dchanges.version=nnn]
34
35 then tweak the formatting if necessary
36 and commit
37
38 The <action> type attribute can be add,update,fix,remove.
39 -->
40
41
42 <document>
43 <properties>
44 <title>Apache Commons Testing Changes</title>
45 </properties>
46 <body>
47
48 <release version="1.0.0" date="2018-MM-DD" description="First release (Java 7)">
49
50 </release>
51
52 </body>
53 </document>