Changes between Version 131 and Version 132 of ReleaseNotes

Timestamp:

21.10.2015 17:43:13 (9 years ago)

Author:

jri

Comment:

4.7 release notes, pt. 4

ReleaseNotes

@@ -7 +7 @@
 == //upcoming//: DeepaMehta 4.7 ==
 
+!DeepaMehta 4.7 is a maintenance release that focuses on both, multi-user server installations, and touch devices.
+
 You can update any !DeepaMehta 4 installation which is not older than !DeepaMehta 4.1. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]].
 
-For plugin developers and server administrators: see the BREAKING CHANGES in the tickets marked in **#bold**.
+3rd-party plugins compatible with !DeepaMehta 4.6.x might be required to be adapted by the respective developers in order to work with !DeepaMehta 4.7. See the BREAKING CHANGES in the tickets marked in **#bold**.
 
 New features:
-* **Private and collaborative file repositories** (#815).
+* **Access controlled file repositories**. In particular private and collaborative file repositories are now supported (#815).
+* Administrators can interactively configure a **Disk Quota** (for file uploads) on a per-user basis (#812).
+* Administrators can **enable/disable user accounts** interactively (#842).
+* The Webclient is usable also on **Touch Devices** (still experimental) (#803).
 
 Improvements:
-* Admins can interactively configure a **Disk Quota** (for file uploads) on a per-user basis (#812).
-* Admins can enable/disable user accounts interactively (#842).
-* Failed uploads are reported to the user (#815).
-
-Bug fixes:
-* Anonymous can browse public file repos (#573).
+* Webclient: the detail panel's resize-handle is more wide and appears visually distinct when grasped. This is beneficial in particular for touch devices (#803).
+* Webclient: failed uploads are reported to the user (#815).
+
+Bug fixes:
+* Anonymous can browse public file repositories (#573).
 * A file whose path contains a "+" character is properly rendered in the detail panel (#819).
 * A folder created by the File Browser's "Create Folder" command show's up in the detail panel immediately (#820).
@@ -26 +30 @@
 
 Changes:
-* We switched back from Pax Web to Felix HTTP due to the way Pax Web handles an OSGi `HttpContext` (#448).
+* We switched back from Pax Web to Felix HTTP. This is because the way Pax Web handles the relationship between an OSGi `HttpContext` and a web session manager. As a consequence private and collaborative DM file repositories do not work with Pax Web (see ticket:815#comment:13).
 * The `dm4.webservice.path` config property allows switching between Pax Web and Felix HTTP without recompiling the Core (#448).
 * The default value for the dm4.filerepo.path config property is `/` instead of empty. `/` regards the entire file system as the DM file repo (**#832**).
@@ -42 +46 @@
     * The DM Core Service can be statically accessed from everywhere. This is useful e.g. in JAX-RS provider classes (#812).
     * Changes in 2 JSON utility methods (**ticket:832#comment:3**).
+    * Bug fixes:
+        * If an error occurs in a plugin's `shutdown()` hook the error is logged and stopping the plugin proceeds (#831).
+        * Core `AccessControl`'s `assignToWorkspace()` method works also for associations (#827).
 * Webservice module:
     * Exception handling is unified for static and dynamic resources, in particular: 1) Logging the exception, and 2) Enriching the response with an error entity (#484).
@@ -48 +55 @@
     * Redesigned search mode extension mechanism (**#839**).
     * `dm4c.open_error_dialog()` opens an error dialog and renders a server response (ticket:815#comment:16).
-* Bug fixes:
-    * If an error occurs in a plugin's `shutdown()` hook the error is logged and stopping the plugin proceeds (#831).
-    * Core `AccessControl`'s `assignToWorkspace()` method works also for associations (#827).
 
 ----