NEWS + version: updated for 1.0 beta 1

1 files changed, 55 insertions, 37 deletions

diff --git a/NEWS b/NEWS
index 6457dc2d..3be8b44d 100644
--- a/NEWS
+++ b/NEWS
@@ -1,38 +1,47 @@
-SyncEvolution 0.9.x -> 1.0 alpha 1, 02.12.2010
+SyncEvolution 0.9.2 -> 1.0 beta 1, 26.01.2010
 ==============================================
 
-A development snapshot, released "because we can" :-)
-
-In particular, we can:
+Compared to the current stable release, 0.9.2, this beta release can also:
 * synchronize directly with a phone over Bluetooth/OBEX
 * accept Bluetooth/OBEX connections in cooperation with obexd 0.19
 * run SyncEvolution as a rudimentary HTTP SyncML server
-* be reasonably sure that it compiles and runs as well as 0.9.x because
-  it passes the same nightly testing without known regressions
-
-The main goal of this release is to get feedback on where we are going
-with 1.0 and its SyncML server and direct synchronization features. If
-you want to get involved, now is a good time because a) there is
-something which works and b) there is still time to influence the
-final 1.0, scheduled for March 2010.
 
-This is definitely work in progress. Only a source snapshot is made
-available, not the usual set of binaries. If you can, compile the latest
-source directly from the git repositories and recheck before reporting
-issues: http://syncevolution.org/development
+These feature were already available in a source-only 1.0 alpha
+release. For the beta, we fixed some issues (nothing major)
+and in addition to the source, also make binaries available. As
+before, we hope to get feedback on where we are going with 1.0 and its
+SyncML server and direct synchronization features. If you want to get
+involved, now is a good time because a) there is something which works
+and b) there is still time to influence the final 1.0, scheduled for
+March 2010.
 
-Documentation is lacking at the moment. Watch the "Development"
+Documentation of the new features can be found in the "Development"
 section (http://syncevolution.org/development) for HOWTOs or ask on
-the mailing list (http://syncevolution.org/support). Contributions
-welcome, as always.
+the mailing list (http://syncevolution.org/support).
 
 Here is a more complete list of features compared to the stable
 release. The full (and up-to-date) list can be retrieved from the
 Moblin Bugzilla (MB) issue tracking system with this query:
 http://bugzilla.moblin.org/showdependencytree.cgi?id=7892&hide_resolved=0
+For changes compared to the 1.0 alpha please consult the
+change log.
 
 Implemented features are marked with a plus +, open ones with a minus -.
 
+ZYB.com
++ now works thanks to a workaround for anchor handling (MB #2424)
+- only contacts tested because everything is considered legacy
+  by ZYB.com
+
+Slow sync handling (MB #2416)
++ Unexpected slow syncs can be detected when running as client and
+  if configured (see "preventSlowSync"), abort the session so that
+  the situation can be analyzed. A refresh from client or server
+  might be more suitable. Because this required manual intervention
+  by the user, the feature is off by default.
+- Catching slow syncs does not work yet when running as server and
+  in one corner case in a client.
+
 Improved sync-UI:
 + settings for HTTP servers are now done inside the list of
   all configs and server templates instead of poping up a
@@ -40,14 +49,19 @@ Improved sync-UI:
 + uses the new D-Bus API
 + no longer uses private gconf key to select default peer,
   replaced by "defaultPeer" in SyncEvolution config
-- the design is a bit tentative and not all of it is implemented;
-  for example, the triangle in front of server entries cannot
-  be used to unfold the entry, only the "setup now" button does
-  that (MB #8315)
-- recovery features like restoring from backup and handling of
-  unexpected slow syncs (MB #2416) are missing
-
-Redesigned and reimplemented D-Bus API:
++ added recovery features like handling of unexpected slow syncs (MB #2416)
+- restoring from backup only supported by command line (MB #8050)
+- spinner to indicate network activity missing (MB #2229)
+- interactive password request not implemented yet (MB #6376)
+
+Command line:
++ fixed printing of rejected items (MB #7755)
++ improved error reporting (textual descriptions instead of plain
+  error codes MB #2069, partial success MB #7755, record and show
+  first ERROR encountered MB #7708)
++ can create new sources (MB #8424)
+
+Redesigned and reimplemented D-Bus API, required by sync-UI:
 + central syncevo-dbus-server controls configurations and sync sessions:
   http://syncevolution.org/development/direct-synchronization-aka-syncml-server
 + accepts incoming SyncML connection requests and messages received by
@@ -58,12 +72,9 @@ Redesigned and reimplemented D-Bus API:
   instead uses gdbus plus automatic C++ binding generated via C++ templates
 - 'syncevolution' command line tool bypasses D-Bus server and runs
   sync sessions itself (MB #5043)
-- waiting for peer not reported over D-Bus and not shown in sync-ui (MB #2229)
-- interactive password request not implemented yet (MB #6376)
 - availability of peers not detected (connected for HTTP, paired for
   Bluetooth; MB #7700)
-- once started, syncevo-dbus-server keeps running forever (MB #7711)
-- restoring backups only possible via command line (MB #8144)
+- Bluetooth peers can only be configured via command line (MB #9216)
 
 Revised configuration layout (MB #8048, design document at
 http://syncevolution.org/development/configuration-handling):
@@ -80,6 +91,9 @@ http://syncevolution.org/development/configuration-handling):
   access them and migrating more than one old configuration causes
   the second or later configuration to loose its "deviceId" property
   (which is shared now), causing a slow sync once
++ config names may contain characters that are not allowed in the
+  file names used for the underlying files; will be replaced with
+  underscores automatically (MB #8350)
 - users of the sync-ui will not know about the --migrate option,
   so if they have only one configuration, it should be migrated
   automatically
@@ -92,16 +106,17 @@ SyncML server in general:
 + different users on the same machine can run their own server,
   as long as they ensure that listening for incoming connections
   does not conflict with each other (different port in HTTP)
++ the session of an HTTP client which stops sending messages expires
+  after "RetryDuration" seconds instead of blocking the server
+  forever (MB #7710)
 - suspend/resume support is untested (MB #2425)
-- an HTTP client which stops sending messages blocks the
-  server forever (MB #7710)
 - automatic backup of server databases is inefficient (done
   even when client is not allowed to do a sync; always backs up
   all data, including sources which are not active; MB #7708)
 - the progress events and statistics reported for a SyncML client
   are not generated when running as SyncML server, will require
   a fair amount of refactoring in the Synthesis engine (MB #7709)
-- the Synthesis serverexample config contains workarounds for
+- the Synthesis server example config contains workarounds for
   specific phones, but SyncEvolution does not currently use those;
   adding new workarounds should be made very simple (MB #7712)
 
@@ -114,10 +129,10 @@ HTTP SyncML server:
 
 OBEX SyncML server ("sync with phones"):
 + peers are contacted via a builtin transport that uses libopenobex (MB #5188)
-+ Server Alerted Notification (SAN) message triggers syncs
++ Server Alerted Notification (SAN) message triggers syncs; server ID
+  and URI are configurable (MB #7871)
 - a configuration must be created for each peer manually, including
-  a syncURL that contains the peer's MAC address (MB #7838) and correct
-  settings for generating the SAN message (MB #7871)
+  a syncURL that contains the peer's MAC address (MB #7838)
 - should be integrated into the system's Bluetooth pairing (MB #7089)
 
 OBEX SyncML client:
@@ -225,6 +240,9 @@ users for 0.9.1:
 - avoid crashes when libecal sets neither error nor pointer (MB#8005)
   and when aborting a running sync in the syncevo-dbus-server (MB#8385)
 
+- "--status" output: fixed missing total item counts (MB #9097)
+
+
 Upgrading from 0.9.1:
 
 * nothing to do, upgrading and downgrading should work seamlessly