Zimbra Desktop 2.0 Beta 2 Release Notes: Difference between revisions
| Line 3: | Line 3: | ||
''Released on April 8, 2010. Notes were last updated on April 8, 2010.'' | ''Released on April 8, 2010. Notes were last updated on April 8, 2010.'' | ||
This is the second beta release of Zimbra Desktop 2.0. There has been no significant new features introduced in this release. Instead, we | This is the second beta release of Zimbra Desktop 2.0. There has been no significant new features introduced in this release. Instead, we placed great emphasis on improving quality, as well as on addressing major known issues found in previous beta release. | ||
Here is a list of most noticeable improvements over beta 1: | Here is a list of most noticeable improvements over beta 1: | ||
| Line 10: | Line 10: | ||
* Fixed the problem of deleted IMAP messages re-appearing as new in Inbox. | * Fixed the problem of deleted IMAP messages re-appearing as new in Inbox. | ||
* Fixed broken mailto handling. User can once again use Zimbra Desktop as default mail application. | * Fixed broken mailto handling. User can once again use Zimbra Desktop as default mail application. | ||
* Fixed missing | * Fixed missing permissions info on shared resources. | ||
* Fixed a few cases of excessive memory usage in calendar sync. | * Fixed a few cases of excessive memory usage in calendar sync. | ||
* Fixed broken spell checker and spelling suggestion in HTML composer. | * Fixed broken spell checker and spelling suggestion in HTML composer. | ||
| Line 16: | Line 16: | ||
* Fixed broken exporting function. | * Fixed broken exporting function. | ||
* Added "Offline Button". User can use it to force Zimbra Desktop go into offline mode (disconnected from network). | * Added "Offline Button". User can use it to force Zimbra Desktop go into offline mode (disconnected from network). | ||
* Added full support for Hotmail POP accounts (UIDL support). | |||
The complete list of fixes is provided in next section of the notes. Since Zimbra Desktop shares majority of the source code with Zimbra Collaboration Suite (ZCS), it has benefited from many of the bug fixes went into recent ZCS 6.0.6 release. Please refer to ZCS release notes for those fixes. | |||
Unfortunately due to resource constraints, there are many known issues we were unable to address in beta 2. The most noticeable ones are listed in "Known Issues" section. We will give high priority for fixing those problems in next release. | |||
== Changes in Beta 2 (build 10414) == | == Changes in Beta 2 (build 10414) == | ||
Revision as of 18:59, 8 April 2010
Overview
Released on April 8, 2010. Notes were last updated on April 8, 2010.
This is the second beta release of Zimbra Desktop 2.0. There has been no significant new features introduced in this release. Instead, we placed great emphasis on improving quality, as well as on addressing major known issues found in previous beta release.
Here is a list of most noticeable improvements over beta 1:
- Added network proxy support. Zimbra Desktop now can use system proxy settings when running behind firewall.
- Fixed the problem of deleted IMAP messages re-appearing as new in Inbox.
- Fixed broken mailto handling. User can once again use Zimbra Desktop as default mail application.
- Fixed missing permissions info on shared resources.
- Fixed a few cases of excessive memory usage in calendar sync.
- Fixed broken spell checker and spelling suggestion in HTML composer.
- Fixed the problem of missing Sent/Draft folders for POP accounts.
- Fixed broken exporting function.
- Added "Offline Button". User can use it to force Zimbra Desktop go into offline mode (disconnected from network).
- Added full support for Hotmail POP accounts (UIDL support).
The complete list of fixes is provided in next section of the notes. Since Zimbra Desktop shares majority of the source code with Zimbra Collaboration Suite (ZCS), it has benefited from many of the bug fixes went into recent ZCS 6.0.6 release. Please refer to ZCS release notes for those fixes.
Unfortunately due to resource constraints, there are many known issues we were unable to address in beta 2. The most noticeable ones are listed in "Known Issues" section. We will give high priority for fixing those problems in next release.
