Roadmap for 4.0

[thet]

Please add your expectations for a 4.0 release here or discuss proposed changes.

API Refactoring

• icalendar should follow more closely the dict and list APIs to access components and iterate over them.
• walk method should deprecated.

Support vcard

Deprecations

• walk method.
• Deprecate modules, functions, etc with https://github.com/zopefoundation/zope.deprecation
  When importing deprecated stuff, which is managed by zope.deprecation, warning messages are logged.

[geier]

+1 for vcard (this could probably be done earlier than 4.0 as it wouldn't break backwards compatibility).

unicode everywhere

I believe we should only handle unicode/str in icalendar.

I'm willing to work on both.

[stlaz]

I suppose the proposed changes (#183) to update to RFC5545 should also make it to major new release. It's been discussed but let's be explicit and have it all here in one topic. Not sure if there's more that will need updating for the newer RFC.
When that is done, strict checking (#28) would be nice to have. Although, it would probably be time demanding so it will not make it there. It's also that kind of a feature that should not bring any backward compatibility breaks so it should not need a major release.

[rnixx]

+1 for more python built-in emulation. another +1 for a long backward compatibility path

[thet]

host documentation on pythonhosted. the current docs on http://icalendar.readthedocs.org/ cannot be updated, because @garbas doesn't find his login credentials anymore.
anyways, pythonhosted is a good place to be.
can actually be done ASAP, no need to wait for a 4.0 release.

[garbas]

@thet i finally found it :)

is thet also your username on readthedocs?

[garbas]

i've added thet as a maintaner

[thet]

@garbas thanks, man! now i have to find my credentials for it ;)

[thet]

We're way past 4.0 :)
Closing this.