[TASK] News.txt Entry for Extbase Property Mapper explicit persisting

Resolves: #47411
Related: #47251
Related: #47182
Releases: 6.1
Change-Id: Ifa6195d6966595e418df159932113a4e09c63af8
Reviewed-on: https://review.typo3.org/20052
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

NEWS.txt

@@ -128,6 +128,17 @@ groups and verify there is now not a bigger number ob objects fetched from
 persistence. To rebuild the previous behavior, revert the TypoScript change of
 https://review.typo3.org/#/c/17879 in your extension.
 
+* Object persistence behaviour changed from implicit to explicit save
+
+Previously, every change to a database driven object got persisted
+automatically at the end of a controller action with a call to persistAll().
+In order to improve performannce and to further narrow the behavior from TYPO3
+Extbase to TYPO3 Flow, this implicit saving has been removed.
+This means that a changed object only gets persisted, if the according
+repository update function gets called for the object.
+As an extension author, please ensure proper usage of the update function
+calls and do not rely on implicit saving anymore.
+
 -------------------------------------------------------------------------------
 Fluid
 -------------------------------------------------------------------------------
@@ -159,4 +170,4 @@ ViewHelper as follows:
 	<f:debug>{key1: 'value1', key2: 'value2'}</f:debug>
 ViewHelpers which were written like this should be re-written to take the array
 as ViewHelper argument:
-	<f:debug value="{key1: 'value1', key2: 'value2'}" />
+	<f:debug value="{key1: 'value1', key2: 'value2'}" />
\ No newline at end of file