blob: b802800b6fa0db70764f6759e1fc74eecf6223d4 [file]
<?xml version="1.0"?>
<!--
Copyright 2002-2004 The Apache Software Foundation or its licensors,
as applicable.
Licensed 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
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE status PUBLIC "-//APACHE//DTD Status V1.3//EN" "status-v13.dtd">
<status>
<developers>
<person name="Volunteer needed" email="dev@forrest.apache.org" id="open"/>
</developers>
<changes>
<!-- Add new releases here -->
<release version="0.1" date="25 May 2005">
<notes>
<p>This plugin encapsulates and extends functionality that was originally in
Forrest Core. With the advent of plugins in Forrest 0.7 we extracted the
functionality for generating changes.xml and todo.xml from the status.xml file. It is
intended that this functionality be extended further within this plugin.</p>
<p>In fact, we have already extended the functionality in a couple of important
ways. See the changelog for more details.</p>
</notes>
<action context="docs" type="add" dev="RDG" importance="high">
Basic documentation on how to create release notes are now included on the
plugins documentation index page.
</action>
<action context="code" type="add" dev="RDG" importance="high">
Added automatic generation of release notes by requesting **/releaseNotes_VERSION-NUMBER.xml
</action>
<action context="design" type="add" dev="RDG" importance="high">
Added optional "notes" element to "release" element of status 1.3 DTD. This
will be inserted into the release notes for that version.
</action>
<action context="code" type="add" dev="RDG" importance="high">
Enable the generation of changes for a specific version by requesting **/changes_VERSION-NUMBER.xml
</action>
<action context="docs" type="fix" dev="DC">
Use relative location of images directory.
</action>
<action dev="DC" type="add" context="design">
Added better sitemap match using regexp to deal
with sub-directories too.
</action>
<action context="code" type="fix" dev="DC">
Replace use of document() function in changes2rss.xml with
sitemap aggregation.
</action>
<action dev="DC" type="fix" context="code"
fixes-bug="FOR-455" due-to="Cyriaque Dupoirieux">
Use the "title" attribute of "changes" and "todo" tags if it exists,
otherwise use the hard-coded values.
</action>
<action context="code" type="update" dev="RDG" importance="high">
Move ToDo and Changes pipelines to this plugin, from core.
</action>
<action dev="RDG" type="add" context="admin">
Initial plugin code.
</action>
</release>
</changes>
<todo>
<actions priority="high">
<action context="code" dev="open">
Add an attribute to the action element in skinconfig called "announce"
with a value of true or false (default to false), and auto generate the
announcement of new features.
</action>
<action context="code" dev="open">
Add an element "upgrade" which contains a textual description of what
actions this change require in order to upgrade from the previous
version and use this to generate the upgrade document.
</action>
<action context="skin" dev="open" type="add">
Create an icon for and action of type "refactor".
</action>
</actions>
<actions priority="med">
<action context="admin" dev="open">
Move DTD's to this plugin from core (depends on having a catalog
extension mechanism for plugins).
</action>
</actions>
<actions priority="low">
<action context="admin" dev="open">
Look at the make sourcetype actions for changes in sitemap.xmap and
either remove them or bring them here as appropriate.
</action>
<action context="admin" type="update" dev="open">
Move images from core to this plugin.
</action>
</actions>
</todo>
</status>