From regebro at codespeak.net Wed Nov 22 18:07:35 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Wed, 22 Nov 2006 18:07:35 +0100 (CET) Subject: [icalendar-checkins] r34866 - iCalendar/trunk/src/icalendar Message-ID: <20061122170735.66FE810075@code0.codespeak.net> Author: regebro Date: Wed Nov 22 18:07:27 2006 New Revision: 34866 Modified: iCalendar/trunk/src/icalendar/caselessdict.py Log: Fixed a bug in caselessdict. Modified: iCalendar/trunk/src/icalendar/caselessdict.py ============================================================================== --- iCalendar/trunk/src/icalendar/caselessdict.py (original) +++ iCalendar/trunk/src/icalendar/caselessdict.py Wed Nov 22 18:07:27 2006 @@ -71,7 +71,7 @@ return dict.pop(self, key.upper(), default) def popitem(self): - return dict.popitem(self, key.upper()) + return dict.popitem(self) def has_key(self, key): return dict.has_key(self, key.upper()) From regebro at codespeak.net Wed Nov 22 18:08:15 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Wed, 22 Nov 2006 18:08:15 +0100 (CET) Subject: [icalendar-checkins] r34867 - iCalendar/trunk Message-ID: <20061122170815.2189710072@code0.codespeak.net> Author: regebro Date: Wed Nov 22 18:08:11 2006 New Revision: 34867 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/HISTORY.txt iCalendar/trunk/version.txt Log: Fixed history and version and such, because this is no longer plain 1.0. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Wed Nov 22 18:08:11 2006 @@ -1,7 +1,7 @@ -iCalendar 1.0 -============= - -* make get_inline and set_inline support non ascii codes. - -* Added support for creating a python egg distribution. +iCalendar 1.1 (unreleased) +========================== +* Fixed a bug in caselessdicts popitem + (thanks to Michael Smith ) + + \ No newline at end of file Modified: iCalendar/trunk/HISTORY.txt ============================================================================== --- iCalendar/trunk/HISTORY.txt (original) +++ iCalendar/trunk/HISTORY.txt Wed Nov 22 18:08:11 2006 @@ -1,3 +1,10 @@ +iCalendar 1.0 (2006-08-03) +========================== + +* make get_inline and set_inline support non ascii codes. + +* Added support for creating a python egg distribution. + iCalendar 0.11 (2005-11-08) =========================== Modified: iCalendar/trunk/version.txt ============================================================================== --- iCalendar/trunk/version.txt (original) +++ iCalendar/trunk/version.txt Wed Nov 22 18:08:11 2006 @@ -1,2 +1,2 @@ -1.0 +1.0+ From regebro at codespeak.net Wed Nov 22 18:40:53 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Wed, 22 Nov 2006 18:40:53 +0100 (CET) Subject: [icalendar-checkins] r34871 - in iCalendar/trunk: . src/icalendar Message-ID: <20061122174053.15F3610064@code0.codespeak.net> Author: regebro Date: Wed Nov 22 18:40:51 2006 New Revision: 34871 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/src/icalendar/cal.py iCalendar/trunk/src/icalendar/prop.py Log: Passing self as a parameter twice doesn't seem useful. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Wed Nov 22 18:40:51 2006 @@ -1,7 +1,7 @@ iCalendar 1.1 (unreleased) ========================== -* Fixed a bug in caselessdicts popitem +* Fixed a bug in caselessdicts popitem. (thanks to Michael Smith ) \ No newline at end of file Modified: iCalendar/trunk/src/icalendar/cal.py ============================================================================== --- iCalendar/trunk/src/icalendar/cal.py (original) +++ iCalendar/trunk/src/icalendar/cal.py Wed Nov 22 18:40:51 2006 @@ -521,6 +521,20 @@ >>> import tempfile, os >>> directory = tempfile.mkdtemp() >>> open(os.path.join(directory, 'test.ics'), 'wb').write(cal.as_string()) + + Test that line breaks do not happen in UTF characters. RFC 2445 is a bit + unclear, it sais that lines may not be longer than 75 *octets* and that + you can split within any *characters*. Some implementation takes this + (quite reasonably) as not allowing splits within multiple-octet UTF-8 + characters. So we need to handle that. + + >>> desc1 = u'PETROL Conference:\\n"Gestion de riesgos en el sector del petr\xf3leo"' + >>> event = Event() + >>> event.add('description', desc1) + + Make sure the unicode of the \xf3 (an o with an accent) exists in the result: + >>> '\xc3\xb3' in event.as_string() + True """ name = 'VCALENDAR' Modified: iCalendar/trunk/src/icalendar/prop.py ============================================================================== --- iCalendar/trunk/src/icalendar/prop.py (original) +++ iCalendar/trunk/src/icalendar/prop.py Wed Nov 22 18:40:51 2006 @@ -980,23 +980,23 @@ unicode.__init__(self, *args, **kwargs) self.params = Parameters() - def escape(self, value): + def escape(self): """ Format value according to iCalendar TEXT escaping rules. """ - return (value.replace('\N', '\n') - .replace('\\', '\\\\') - .replace(';', r'\;') - .replace(',', r'\,') - .replace('\r\n', r'\n') - .replace('\n', r'\n') - ) + return (self.replace('\N', '\n') + .replace('\\', '\\\\') + .replace(';', r'\;') + .replace(',', r'\,') + .replace('\r\n', r'\n') + .replace('\n', r'\n') + ) def __repr__(self): return u"vText(%s)" % unicode.__repr__(self) def ical(self): - return self.escape(self).encode(self.encoding) + return self.escape().encode(self.encoding) def from_ical(ical): "Parses the data format from ical text format" From regebro at codespeak.net Wed Nov 22 19:37:31 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Wed, 22 Nov 2006 19:37:31 +0100 (CET) Subject: [icalendar-checkins] r34874 - iCalendar/trunk/src/icalendar Message-ID: <20061122183731.D6D5610063@code0.codespeak.net> Author: regebro Date: Wed Nov 22 19:37:29 2006 New Revision: 34874 Modified: iCalendar/trunk/src/icalendar/cal.py Log: A temporary test was checked in by mistake. Modified: iCalendar/trunk/src/icalendar/cal.py ============================================================================== --- iCalendar/trunk/src/icalendar/cal.py (original) +++ iCalendar/trunk/src/icalendar/cal.py Wed Nov 22 19:37:29 2006 @@ -521,20 +521,6 @@ >>> import tempfile, os >>> directory = tempfile.mkdtemp() >>> open(os.path.join(directory, 'test.ics'), 'wb').write(cal.as_string()) - - Test that line breaks do not happen in UTF characters. RFC 2445 is a bit - unclear, it sais that lines may not be longer than 75 *octets* and that - you can split within any *characters*. Some implementation takes this - (quite reasonably) as not allowing splits within multiple-octet UTF-8 - characters. So we need to handle that. - - >>> desc1 = u'PETROL Conference:\\n"Gestion de riesgos en el sector del petr\xf3leo"' - >>> event = Event() - >>> event.add('description', desc1) - - Make sure the unicode of the \xf3 (an o with an accent) exists in the result: - >>> '\xc3\xb3' in event.as_string() - True """ name = 'VCALENDAR' From regebro at codespeak.net Wed Nov 22 19:40:33 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Wed, 22 Nov 2006 19:40:33 +0100 (CET) Subject: [icalendar-checkins] r34875 - in iCalendar/trunk: . src/icalendar Message-ID: <20061122184033.F099910063@code0.codespeak.net> Author: regebro Date: Wed Nov 22 19:40:32 2006 New Revision: 34875 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/src/icalendar/parser.py Log: Fixed the UTF-8 line folding bug. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Wed Nov 22 19:40:32 2006 @@ -4,4 +4,11 @@ * 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 Modified: iCalendar/trunk/src/icalendar/parser.py ============================================================================== --- iCalendar/trunk/src/icalendar/parser.py (original) +++ iCalendar/trunk/src/icalendar/parser.py Wed Nov 22 19:40:32 2006 @@ -261,6 +261,11 @@ >>> c '123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 ' + We do not fold withing a UTF-8 character: + >>> c = Contentline('This line has a UTF-8 character where it should be folded. Make sure it g\xc3\xabts folded before that character.') + >>> '\xc3\xab' in str(c) + True + It can parse itself into parts. Which is a tuple of (name, params, vals) >>> c = Contentline('dtstart:20050101T120000') @@ -354,6 +359,7 @@ >>> c = Contentline('key;param="pValue":value', strict=True) >>> c.parts() ('key', Parameters({'PARAM': 'pValue'}), 'value') + """ def __new__(cls, st, strict=False): @@ -417,8 +423,29 @@ "Long content lines are folded so they are less than 75 characters wide" l_line = len(self) new_lines = [] - for i in range(0, l_line, 74): - new_lines.append(self[i:i+74]) + start = 0 + end = 74 + while True: + if end > l_line: + end = l_line + else: + # Check that we don't fold in the middle of a UTF-8 character: + # http://lists.osafoundation.org/pipermail/ietf-calsify/2006-August/001126.html + while True: + char_value = ord(self[end]) + if char_value < 128 or char_value >= 192: + # This is not in the middle of a UTF-8 character, so we + # can fold here: + break + else: + end -= 1 + + new_lines.append(self[start:end]) + if end == l_line: + # Done + break + start = end + end = start + 74 return '\r\n '.join(new_lines) From regebro at codespeak.net Thu Nov 23 13:33:23 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 13:33:23 +0100 (CET) Subject: [icalendar-checkins] r34888 - iCalendar/trunk Message-ID: <20061123123323.B5E9610060@code0.codespeak.net> Author: regebro Date: Thu Nov 23 13:33:21 2006 New Revision: 34888 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/CREDITS.txt iCalendar/trunk/version.txt Log: Preparing for release of 1.1. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Thu Nov 23 13:33:21 2006 @@ -1,4 +1,4 @@ -iCalendar 1.1 (unreleased) +iCalendar 1.1 (2006-11-23) ========================== * Fixed a bug in caselessdicts popitem. Modified: iCalendar/trunk/CREDITS.txt ============================================================================== --- iCalendar/trunk/CREDITS.txt (original) +++ iCalendar/trunk/CREDITS.txt Thu Nov 23 13:33:21 2006 @@ -20,4 +20,6 @@ - Olivier Grisel (ogrisel at nuxeo.com) +- Michael Smith + Thanks to codespeak for hosting this project. Modified: iCalendar/trunk/version.txt ============================================================================== --- iCalendar/trunk/version.txt (original) +++ iCalendar/trunk/version.txt Thu Nov 23 13:33:21 2006 @@ -1,2 +1,2 @@ -1.0+ +1.1 From regebro at codespeak.net Thu Nov 23 13:34:47 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 13:34:47 +0100 (CET) Subject: [icalendar-checkins] r34889 - iCalendar/tag/iCalendar-1.1 Message-ID: <20061123123447.EAD3910060@code0.codespeak.net> Author: regebro Date: Thu Nov 23 13:34:46 2006 New Revision: 34889 Added: iCalendar/tag/iCalendar-1.1/ - copied from r34888, iCalendar/trunk/ Log: Releasing 1.1. From regebro at codespeak.net Thu Nov 23 13:39:03 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 13:39:03 +0100 (CET) Subject: [icalendar-checkins] r34890 - iCalendar/tag/iCalendar-1.1 Message-ID: <20061123123903.1BCAB10060@code0.codespeak.net> Author: regebro Date: Thu Nov 23 13:39:02 2006 New Revision: 34890 Removed: iCalendar/tag/iCalendar-1.1/ Log: Nope, not ready, I need to update the README first. From regebro at codespeak.net Thu Nov 23 13:39:36 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 13:39:36 +0100 (CET) Subject: [icalendar-checkins] r34891 - iCalendar/trunk Message-ID: <20061123123936.5D87A10060@code0.codespeak.net> Author: regebro Date: Thu Nov 23 13:39:35 2006 New Revision: 34891 Modified: iCalendar/trunk/README.txt Log: Preparing for 1.1. Modified: iCalendar/trunk/README.txt ============================================================================== --- iCalendar/trunk/README.txt (original) +++ iCalendar/trunk/README.txt Thu Nov 23 13:39:35 2006 @@ -26,11 +26,14 @@ News ==== +* 2006-11-23: `iCalendar 1.1`_ released (`changes for 1.1`_) * 2006-08-03: `iCalendar 1.0`_ released (`changes for 1.0`_) * 2005-11-08: `iCalendar 0.11`_ released (`changes for 0.11`_) * 2005-04-28: `iCalendar 0.10`_ released (`changes for 0.10`_) -.. _`iCalendar 1.0`: iCalendar-0.11.tgz +.. _`iCalendar 1.1`: iCalendar-1.1.tgz +.. _`changes for 1.1`: changes-1.1.html +.. _`iCalendar 1.0`: iCalendar-1.0.tgz .. _`changes for 1.0`: changes-1.0.html .. _`iCalendar 0.11`: iCalendar-0.11.tgz .. _`changes for 0.11`: changes-0.11.html @@ -108,6 +111,8 @@ Download ======== +* `iCalendar 1.1`_ (2006-11-23) +* `iCalendar 1.0`_ (2006-08-03) * `iCalendar 0.11`_ (2005-08-11) * `iCalendar 0.10`_ (2005-04-28) From regebro at codespeak.net Thu Nov 23 14:09:42 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 14:09:42 +0100 (CET) Subject: [icalendar-checkins] r34892 - iCalendar/tag/iCalendar-1.1 Message-ID: <20061123130942.394A710061@code0.codespeak.net> Author: regebro Date: Thu Nov 23 14:09:40 2006 New Revision: 34892 Added: iCalendar/tag/iCalendar-1.1/ - copied from r34891, iCalendar/trunk/ Log: Releasing 1.1 From regebro at codespeak.net Thu Nov 23 15:10:55 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 15:10:55 +0100 (CET) Subject: [icalendar-checkins] r34895 - iCalendar/www Message-ID: <20061123141055.C006610063@code0.codespeak.net> Author: regebro Date: Thu Nov 23 15:10:51 2006 New Revision: 34895 Added: iCalendar/www/HOWTO.txt (contents, props changed) Log: How to relase icalendar and update the website. Added: iCalendar/www/HOWTO.txt ============================================================================== --- (empty file) +++ iCalendar/www/HOWTO.txt Thu Nov 23 15:10:51 2006 @@ -0,0 +1,97 @@ +iCalendar release instructions: +=============================== + +Reqirements: +------------ +* EasyInstall Egg support for setuptools: + http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install + +* docutils 0.4: + easy_install docutils + + +How to make a release: +---------------------- +0. Update version.txt. + +1. First update the CHANGES.txt, so that the top line states the version you + intend to release and todays date. Like so: + + iCalendar 1.2 (2007-04-01) + + Test that the CHANGES.txt is fine by generating and HTML file and + checking it out in a browser: + + rst2html.py --stylesheet=http://codespeak.net/icalendar/style.css --link-stylesheet CHANGES.txt > /tmp/changes.html + firefox /tmp/changes.html + +2. Update the README.txt by adding new lines for the new versions when it + comes to change-files and tar files. Test that the README.txt is fine by + generating and HTML file and checking it out in a browser: + + rst2html.py --stylesheet=http://codespeak.net/icalendar/style.css --link-stylesheet README.txt > /tmp/index.html + firefox /tmp/index.html + + Also check that contributors.txt and install.txt are all OK, but usually + you shouldn't need to change them. + +3. Commit everything. + +4. Copy trunk to the new version: + svn cp http://codespeak.net/svn/iCalendar/trunk http://codespeak.net/svn/iCalendar/tag/iCalendar-1.2 + +5. Update the website (see below). + +6. Generate the egg and upload it to CheezeShop (if you can. Maybe you have to + be me (regebro). I don't know. + + python setup.py bdist_egg + +7. Copy the contents of the changes file to the history file, and commit that. + + +How to update the iCalendar website after a release: +---------------------------------------------------- + +1. Export the new version of iCalendar somewhere: + cd /tmp + svn export http://codespeak.net/svn/iCalendar/tag/iCalendar-1.2 + +2. Make a tar: tgz cvfz iCalendar-1.2.tgz iCalendar-1.2 + +3. Generate the website with the publish.py script. Ex: + python publish.py /tmp/icalendarweb /tmp/iCalendar-1.2 1.2 + +4. Copy the tar into the newly generated directory: + cp /tmp/iCalendar-1.2.tgz /tmp/icalendarweb + +5. Sync it over to the codespeak server: + rsync -e ssh -Prvz /tmp/icalendarweb/* yourusername at codespeak.net:/www/codespeak.net/htdocs/icalendar + + +How to regenerate the iCalendar website from scratch: +----------------------------------------------------- + +1. Export ALL the versions of icalendar (or at least the ones you plan to have + a tgz of on the site): + cd /tmp + svn export http://codespeak.net/svn/iCalendar/tag/ + +2. Make a tar for each release: + cd /tmp/tag + tgz cvfz iCalendar-0.10.tgz iCalendar-0.10 + tgz cvfz iCalendar-0.11.tgz iCalendar-0.11 + ...and so on. + +3. Generate the website with the publish.py script, once for every version, + starting with the lowest one: + python publish.py /tmp/icalendarweb /tmp/iCalendar-0.10 0.10 + python publish.py /tmp/icalendarweb /tmp/iCalendar-0.11 0.11 + ...and do up until the last release. + +4. Copy the tar files into the newly generated directory: + cp /tmp/tag/*.tgz /tmp/icalendarweb + +5. Sync it over to the codespeak server: + rsync -e ssh -Prvz /tmp/icalendarweb/* yourusername at codespeak.net:/www/codespeak.net/htdocs/icalendar + From regebro at codespeak.net Thu Nov 23 15:12:54 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 15:12:54 +0100 (CET) Subject: [icalendar-checkins] r34896 - iCalendar/trunk Message-ID: <20061123141254.ABEA910069@code0.codespeak.net> Author: regebro Date: Thu Nov 23 15:12:51 2006 New Revision: 34896 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/HISTORY.txt iCalendar/trunk/version.txt Log: Finishing off the 1.1 release. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Thu Nov 23 15:12:51 2006 @@ -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 Modified: iCalendar/trunk/HISTORY.txt ============================================================================== --- iCalendar/trunk/HISTORY.txt (original) +++ iCalendar/trunk/HISTORY.txt Thu Nov 23 15:12:51 2006 @@ -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) ========================== Modified: iCalendar/trunk/version.txt ============================================================================== --- iCalendar/trunk/version.txt (original) +++ iCalendar/trunk/version.txt Thu Nov 23 15:12:51 2006 @@ -1,2 +1 @@ -1.1 - +1.1+ From regebro at codespeak.net Thu Nov 23 17:22:44 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Thu, 23 Nov 2006 17:22:44 +0100 (CET) Subject: [icalendar-checkins] r34910 - in iCalendar/trunk: . src/icalendar Message-ID: <20061123162244.A832C10063@code0.codespeak.net> Author: regebro Date: Thu Nov 23 17:22:41 2006 New Revision: 34910 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/src/icalendar/parser.py Log: * The bugfix for the folding of line in the middle of UTF-8 characters included another bug, which is now fixed. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Thu Nov 23 17:22:41 2006 @@ -1,4 +1,4 @@ iCalendar 1.2 (unreleased) ========================== -No changes yet. \ No newline at end of file +* Fixed a string index out of range error in the new folding code. \ No newline at end of file Modified: iCalendar/trunk/src/icalendar/parser.py ============================================================================== --- iCalendar/trunk/src/icalendar/parser.py (original) +++ iCalendar/trunk/src/icalendar/parser.py Thu Nov 23 17:22:41 2006 @@ -261,11 +261,14 @@ >>> c '123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 ' - We do not fold withing a UTF-8 character: + We do not fold within a UTF-8 character: >>> c = Contentline('This line has a UTF-8 character where it should be folded. Make sure it g\xc3\xabts folded before that character.') >>> '\xc3\xab' in str(c) True + Don't fail if we fold a line that is exactly X times 74 characters long: + >>> c = str(Contentline(''.join(['x']*148))) + It can parse itself into parts. Which is a tuple of (name, params, vals) >>> c = Contentline('dtstart:20050101T120000') @@ -426,7 +429,7 @@ start = 0 end = 74 while True: - if end > l_line: + if end >= l_line: end = l_line else: # Check that we don't fold in the middle of a UTF-8 character: From regebro at codespeak.net Sat Nov 25 13:18:54 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Sat, 25 Nov 2006 13:18:54 +0100 (CET) Subject: [icalendar-checkins] r34953 - iCalendar/trunk Message-ID: <20061125121854.6AACE10077@code0.codespeak.net> Author: regebro Date: Sat Nov 25 13:18:51 2006 New Revision: 34953 Modified: iCalendar/trunk/CHANGES.txt iCalendar/trunk/README.txt iCalendar/trunk/version.txt Log: Preparing for release of 1.2. Modified: iCalendar/trunk/CHANGES.txt ============================================================================== --- iCalendar/trunk/CHANGES.txt (original) +++ iCalendar/trunk/CHANGES.txt Sat Nov 25 13:18:51 2006 @@ -1,4 +1,4 @@ -iCalendar 1.2 (unreleased) +iCalendar 1.2 (2006-11-25) ========================== -* Fixed a string index out of range error in the new folding code. \ No newline at end of file +* Fixed a string index out of range error in the new folding code. Modified: iCalendar/trunk/README.txt ============================================================================== --- iCalendar/trunk/README.txt (original) +++ iCalendar/trunk/README.txt Sat Nov 25 13:18:51 2006 @@ -26,11 +26,14 @@ News ==== +* 2006-11-26: `iCalendar 1.2`_ released (`changes for 1.2`_) * 2006-11-23: `iCalendar 1.1`_ released (`changes for 1.1`_) * 2006-08-03: `iCalendar 1.0`_ released (`changes for 1.0`_) * 2005-11-08: `iCalendar 0.11`_ released (`changes for 0.11`_) * 2005-04-28: `iCalendar 0.10`_ released (`changes for 0.10`_) +.. _`iCalendar 1.2`: iCalendar-1.2.tgz +.. _`changes for 1.2`: changes-1.2.html .. _`iCalendar 1.1`: iCalendar-1.1.tgz .. _`changes for 1.1`: changes-1.1.html .. _`iCalendar 1.0`: iCalendar-1.0.tgz @@ -111,6 +114,7 @@ Download ======== +* `iCalendar 1.2`_ (2006-11-26) * `iCalendar 1.1`_ (2006-11-23) * `iCalendar 1.0`_ (2006-08-03) * `iCalendar 0.11`_ (2005-08-11) Modified: iCalendar/trunk/version.txt ============================================================================== --- iCalendar/trunk/version.txt (original) +++ iCalendar/trunk/version.txt Sat Nov 25 13:18:51 2006 @@ -1 +1 @@ -1.1+ +1.2 From regebro at codespeak.net Sat Nov 25 13:20:37 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Sat, 25 Nov 2006 13:20:37 +0100 (CET) Subject: [icalendar-checkins] r34954 - iCalendar/tag/iCalendar-1.2 Message-ID: <20061125122037.61ACE10077@code0.codespeak.net> Author: regebro Date: Sat Nov 25 13:20:35 2006 New Revision: 34954 Added: iCalendar/tag/iCalendar-1.2/ - copied from r34953, iCalendar/trunk/ Log: Releasing 1.2 From regebro at codespeak.net Sat Nov 25 14:16:33 2006 From: regebro at codespeak.net (regebro at codespeak.net) Date: Sat, 25 Nov 2006 14:16:33 +0100 (CET) Subject: [icalendar-checkins] r34958 - iCalendar/www Message-ID: <20061125131633.13C4B10077@code0.codespeak.net> Author: regebro Date: Sat Nov 25 14:16:30 2006 New Revision: 34958 Modified: iCalendar/www/HOWTO.txt Log: HOWTO fixes. Modified: iCalendar/www/HOWTO.txt ============================================================================== --- iCalendar/www/HOWTO.txt (original) +++ iCalendar/www/HOWTO.txt Sat Nov 25 14:16:30 2006 @@ -43,9 +43,11 @@ 5. Update the website (see below). 6. Generate the egg and upload it to CheezeShop (if you can. Maybe you have to - be me (regebro). I don't know. + be me (regebro) to upload the files. I don't know. + python setup.py register python setup.py bdist_egg + + manual upload of egg and tgz (see below of how to make the tgz) 7. Copy the contents of the changes file to the history file, and commit that. @@ -57,7 +59,7 @@ cd /tmp svn export http://codespeak.net/svn/iCalendar/tag/iCalendar-1.2 -2. Make a tar: tgz cvfz iCalendar-1.2.tgz iCalendar-1.2 +2. Make a tar: tar cvfz iCalendar-1.2.tgz iCalendar-1.2 3. Generate the website with the publish.py script. Ex: python publish.py /tmp/icalendarweb /tmp/iCalendar-1.2 1.2