Skip to content
Browse files
Add missing changes.xml file.
  • Loading branch information
garydgregory committed Oct 30, 2017
1 parent c4c0308 commit b73edce61758c311ec163cd86c12a113595f9985
Showing 1 changed file with 86 additions and 0 deletions.
@@ -0,0 +1,86 @@
<?xml version="1.0"?>
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

This file is used by the maven-changes-plugin to generate the release notes.
Useful ways of finding items to add to this file are:
1. Add items when you fix a bug or add a feature (this makes the
release process easy :-).
2. Do a Jira search for tickets closed since the previous release.
3. Use the report generated by the maven-changelog-plugin to see all
SVN commits. Set the' maven.changelog.range
property to the number of days since the last release.
To generate the release notes from this file:
mvn changes:announcement-generate -Prelease-notes [-Dchanges.version=nnn]
then tweak the formatting if necessary
and commit
The <action> type attribute can be add,update,fix,remove.

<title>Apache Commons RDF Release Notes</title>
<!-- NOTE:
The description below is specially formatted so as to improve the layout of the generated release notes:
The parsing process removes all line feeds, replacing them with a single space.
The Velocity template in src/changes has been enhanced to replace pairs of adjacent spaces
with a new-line in the release notes. (These spaces are ignored when displaying HTML).
If the output is not quite correct, check for invisible trailing spaces!
N.B. The release notes template groups actions by type, and only extracts data for the current release.
The changes report outputs actions in the order they appear in this file.
To regenerate the release notes:
mvn changes:announcement-generate -Prelease-notes [-Dchanges.version=nnn]
Defining changes.version allows one to create the RN without first removing the SNAPSHOT suffix.

<release version="0.5.0" date="YYYY-MM-DD" description="Minor feature and bug fix release.">
<!-- TODO -->

<release version="0.4.0" date="2017-10-29" description="DO NOT USE, this release was not approved by the Project Management Commitee">
<!-- TODO -->

<release version="0.3.0-incubating" date="YYYY-MM-DD" description="Minor feature and bug fix release.">
<!-- TODO -->

<release version="0.2.0-incubating" date="YYYY-MM-DD" description="Minor feature and bug fix release.">
<!-- TODO -->

<release version="0.1.0-incubating" date="YYYY-MM-DD" description="Initial Release">
<action type="add">
Initial Release.


0 comments on commit b73edce

Please sign in to comment.