From 8ccf40cdecf33c827efaa469fa51c8aaee5135d1 Mon Sep 17 00:00:00 2001 From: Lennart Regebro Date: Thu, 23 Nov 2006 14:12:51 +0000 Subject: [PATCH] Finishing off the 1.1 release. --- CHANGES.txt | 14 ++------------ HISTORY.txt | 15 +++++++++++++++ version.txt | 3 +-- 3 files changed, 18 insertions(+), 14 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 7b078fe..e1e7fc3 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,14 +1,4 @@ -iCalendar 1.1 (2006-11-23) +iCalendar 1.2 (unreleased) ========================== -* Fixed a bug in caselessdicts popitem. - (thanks to Michael Smith ) - -* The RFC 2445 was a bit unclear on how to handle line folding when it - happened to be in the middle of a UTF-8 character. This has been clarified - in the following discussion: - http://lists.osafoundation.org/pipermail/ietf-calsify/2006-August/001126.html - And this is now implemented in iCalendar. It will not fold in the middle - of a UTF-8 character, but may fold in the middle of a UTF-8 composing - character sequence. - \ No newline at end of file +No changes yet. \ No newline at end of file diff --git a/HISTORY.txt b/HISTORY.txt index 991408d..d731864 100644 --- a/HISTORY.txt +++ b/HISTORY.txt @@ -1,3 +1,18 @@ +iCalendar 1.1 (2006-11-23) +========================== + +* Fixed a bug in caselessdicts popitem. + (thanks to Michael Smith ) + +* The RFC 2445 was a bit unclear on how to handle line folding when it + happened to be in the middle of a UTF-8 character. This has been clarified + in the following discussion: + http://lists.osafoundation.org/pipermail/ietf-calsify/2006-August/001126.html + And this is now implemented in iCalendar. It will not fold in the middle + of a UTF-8 character, but may fold in the middle of a UTF-8 composing + character sequence. + + iCalendar 1.0 (2006-08-03) ========================== diff --git a/version.txt b/version.txt index f5f9421..c7b4ccb 100644 --- a/version.txt +++ b/version.txt @@ -1,2 +1 @@ -1.1 - +1.1+