Bug #986

Template for the next release

Added by matthias almost 7 years ago. Updated almost 7 years ago.

Status:ClosedStart date:
Priority:LowDue date:
Assignee:-% Done:


Target version:-



I want to commit the following template of the release page to site/ if
nobody objects:


The purpose to commit the template this early is easy. If any of our
developers made a significant commit/change/$whatever (which is
important enough to get mentioned in the release notes) he could add it
to the list. This could save us some time and no changes will be lost
:) Feel free to add/remove categories.

I assumed that the next release is called 2.0. If its not 2.0 we could
easily rename the file and change the version numbers in the doc. Of
course the document is not connected to the build, we don't want to create
any confusion :)




#1 Updated by steve almost 7 years ago

On Mon, 7 Apr 2008 19:00:53 +0200
Matthias Schmidt <> wrote:

A couple of little nits:

"Release Notes for DragonFly 1.12.x"

I don't think the README link should point into CVS, come 4.11 it
will probably be horribly wrong for 2.0.

#2 Updated by hasso almost 7 years ago


Also available in: Atom PDF