163f1eefc4
in accounts.sync() we would holdordropconnections() after each sync. But depending on the repository configuration that might imply that offlineimap tries to keep the same connections. But when a sync failed, e.g. after a user had his computer suspended, it might be that our connections that we have are worthless. So definitely drop them after a failed sync. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
43 lines
936 B
ReStructuredText
43 lines
936 B
ReStructuredText
=========
|
|
ChangeLog
|
|
=========
|
|
|
|
Users should ignore this content: **it is draft**.
|
|
|
|
Contributors should add entries here in the following section, on top of the
|
|
others.
|
|
|
|
`WIP (coming releases)`
|
|
=======================
|
|
|
|
New Features
|
|
------------
|
|
|
|
Changes
|
|
-------
|
|
|
|
* Reduced our sync logic from 4 passes to 3 passes (integrating upload of
|
|
"new" and "existing" messages into one function). This should result in a
|
|
slight speedup.
|
|
|
|
Bug Fixes
|
|
---------
|
|
|
|
* Drop connection if synchronisation failed. This is needed if resuming the
|
|
system from suspend mode gives a wrong connection.
|
|
|
|
|
|
Pending for the next major release
|
|
==================================
|
|
|
|
* UIs get shorter and nicer names. (API changing)
|
|
* Implement IDLE feature. (delayed until next major release)
|
|
|
|
|
|
Stalled
|
|
=======
|
|
|
|
* Learn Sqlite support.
|
|
Stalled: it would need to learn the ability to choose between the current
|
|
format and SQL to help testing the long term.
|