From 982ea06e104284d3a3db2f14b23780f529d33528 Mon Sep 17 00:00:00 2001 From: Stef Walter Date: Wed, 16 Jun 2010 18:29:45 +0000 Subject: Release version 0.2.1 --- ChangeLog | 36 +++++++++++++++++++++++++++++++----- 1 file changed, 31 insertions(+), 5 deletions(-) (limited to 'ChangeLog') diff --git a/ChangeLog b/ChangeLog index 96f9d77..0bd7f42 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,32 @@ -Version 0.2 [2008-07-02] - - Lookup zone name properly - - Fix crashers and build problems +=== ChangeLog discontinued === -Version 0.1 - - Initial version + With the move to git, this project is switching from a ChangeLog + file to relying on commit messages to provide change history. Please + write commit messages in the following format: + +=== begin example commit === + + Short explanation of the commit + + Longer explanation explaining exactly what's changed, whether any + external or private interfaces changed, what bugs were fixed (with bug + tracker reference if applicable) and so forth. Be concise but not too + brief. + +=== end example commit === + + - Always add a brief description of the commit to the _first_ line of + the commit and terminate by two newlines. This may be the title of + a fixed bug, copied from Bugzilla. + + - First line (the brief description) must only be one sentence and + should start with a capital letter unless it starts with a + lowercase symbol or identifier. Don't use a trailing full stop, + and don't exceed 72 characters. + + - The main description (the body) is normal prose and should use + normal punctuation and capital letters where appropriate. + + - When committing code on behalf of others use the --author option, + e.g. git commit -a --author "Joe Coder " and + --signoff. -- cgit v1.2.3