* Use of jQuery in place of Mootools
* Most of the custom mootools plugins have been ported to jQuery
* Use of bootstrap from Twitter in place of the old CSS
* Most of the admin templates have been reworked
* The sievefilters extension has been ported
* The postfix autoreply extension is almost done
* more...
see #204
* Added support for migrations
* Big refactoring of the admin code
done: Support for SHA256 algorithm to store passwords (fix#195)
done: admin models refactoring (fix#196)
* We now make a difference between users that own a specific object and users that have access to a specific object
* Limits are not moved anymore (from one reseller to a domain admin) when we grant access to a domain
see #105
* Demo application : set the managesieve authentication mechanism to 'PLAIN' by default because the dovecot version provided with Debian squeeze is a buggy one.
A new admin parameter is available to specify the default application that will be launched when no one is present in the url. (ie. when the top level "/" is called).
fixed#165
* Some strings were not detected by makemessages (for example in javascript files, behind comments...). There are still some issues with that but I think I'll have to wait a future Django release.
* Support for per-user language selection is almost done.
see #166
Work in progress:
* New domains admin page, all menus are now at the same level,
* Views, models and forms partial refactoring (better code organization).
new: parameters module refactored. The API is more simple now, there is no need to provide a module name anymore, this last is automatically guessed. Also, a new 'label' field can be provide when declaring a new parameter. It will be used instead of the name.
new: email parsing refactored. My first attempt was really ugly. I did not really studied the various RFC describing how messages are formatted or what IMAP fetch queries can do. Now, I hope this new code will face better unknown types. At least, It will be simpler to update.
wip: #36, using tinyMCE (django-tinymce) to write messages in HTML. Currently, compose a new message is working pretty well. Answering or forwarding a message is still a mess...
* The bigger one concerns fixtures. As django 1.2 resolves it by implementing natural keys, it's becoming a requirement.
* There was also problems 0002_auto__del_field_alias_mbox, my bad...
* It was possible to create aliases that point to addresses of other domains!
* Some path problems in the stats module.
* Some path problems with the autoreply.
perms object is no longer passed to builtins or filters, we use user instead
(it seems that perms content is different with Django 1.2)
#48 : I think I've found a way to include templatetags dynamically, using add_to_builtins.
This is not finished yet. More work than what I expected but the main part is done.
It will need a lot of testing... There is still a bug when activating a new extension
in development mode (ie. with python web server), I think it does not occur behind
a real web server.
Antoine Nguyen