Changes between Version 117 and Version 118 of ReleaseNotes


Ignore:
Timestamp:
03.02.2015 05:40:12 (10 years ago)
Author:
jri
Comment:

4.5 release notes, pt. 3

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseNotes

    v117 v118  
    77== 2015-02-?: DeepaMehta 4.5 == 
    88 
     9!DeepaMehta 4.5 is a major release that features a redesigned **Access Control** system that underlies DeepaMehta's sharing functionality. Sharing is governed by ''Workspaces'' which connect users to content. A **''Workspace Sharing Mode''** lets the user control how (if at all) the workspace content is accessible by others. To accommodate typical sharing scenarios 5 sharing modes are pre-defined: "Private", "Confidential", "Collaborative", "Public", and "Common". For the first time a !DeepaMehta installation can hold private and shared data at the same time. 
     10 
     11The new access control concepts are described in this posting: 
     12http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2014-December/000562.html\\ 
     13Further details are described here: 
     14http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2015-January/000570.html 
     15 
     16For plugin developers the highlight feature of !DeepaMehta 4.5 is **Service injection for migrations**. This supports the development of upgradable plugins. 
     17 
     18You can upgrade any !DeepaMehta 4 standard installation which is not older than !DeepaMehta 4.1. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]]. 3rd-party plugins compatible with !DeepaMehta 4.4 might be required to be adapted in order to work in DeepaMehta 4.5. 
     19 
    920New features: 
    10 * **Elaborated Access Control** (#592). 
    11     * **Configurable access realms**: the ''Workspace Sharing Mode'' let the user control how (if at all) the workspace content is accessible by others. 
    12     * **Private Sphere**. 
    13     * The new access control concepts are described in this posting: http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2014-December/000562.html 
    14     Further details are described here: 
    15     http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2015-January/000570.html 
     21* **Redesigned Access Control** (#592). 
     22    * User configurable access realms by the means of ''Workspace Sharing Modes''. 
     23    * The Webclient GUI presents workspaces as well-defined spaces between the user can switch. 
     24    * True private sphere. 
    1625* 2 new context menu commands 
    17     * ''Assign to Workspace'': allows the user to assign a topic/association to another workspace and thus changing its accessibility (#592). 
     26    * "Assign to Workspace": allows the user to assign a topic/association to another workspace and thus changing its accessibility (#592). 
    1827    * "Get Info": shows creator/modifier/owner info and timestamps for a topic or association (#747, #749). 
    1928 
    2029Plugin Development Framework: 
    21 * **Service injection to migrations** (#324). 
     30* **Service injection for migrations** (#324). 
    2231* Core API provides a generic `getObject(id)` method (#760). 
    2332* Workspaces module: 
    … …  
    2534    * The Workspaces API is RESTful (#592). 
    2635* Webclient GUIToolkit: items rendered by `topic_menu()` can be disabled by the means of an indicator function (#755). 
    27 * Client-side Access Control events: 
    28     * The `logged_in` and `logged_out` events are replaces by `authority_increased` and `authority_decreased` with extended semantics (#592). 
    29     * `authority_decreased_2` 
     36* Client-side Access Control events (#592): 
     37    * The `logged_in` and `logged_out` events are replaced by `authority_increased` and `authority_decreased` with extended semantics. 
     38    * 2 ''logout levels'' (in shape of the `authority_decreased` and `authority_decreased_2` events) allow plugin's to orchestrate their logout actions.  
    3039* The server-side `postInstall()` hook is dropped. You can do the same with a migration now (#324). 
    3140 
    … …  
    3645Bug fixes: 
    3746* The ''Create Association'' operation is only available if the user has the corresponding permission (#592). 
    38  
    39 You can update any !DeepaMehta 4 standard installation which is not older than !DeepaMehta 4.1. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]]. 3rd-party plugins compatible with !DeepaMehta 4.4 might be required to be adapted in order to work in DeepaMehta 4.5. 
    4047 
    4148----