Last modified by Thomas Mortagne on 2017/03/24

From version 17.1
edited by Thomas Mortagne
on 2015/05/18
Change comment: There is no comment for this version
To version 18.3
edited by Eduard Moraru
on 2015/05/18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ThomasMortagne
1 +XWiki.enygma
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  This is the release notes for [[XWiki Commons>>http://commons.xwiki.org]], [[XWiki Rendering>>http://rendering.xwiki.org]], [[XWiki Platform>>http://platform.xwiki.org]] and [[XWiki Enterprise>>http://enterprise.xwiki.org]]. They share the same release notes as they are released together and have the same version.
6 6  
7 -<insert description of release here>
7 +This second milestone release brings a new flavors mechanism prototype and a new debug mode, together with a couple of mail and job module under-the-hood improvements.
8 8  
9 9  = New and Noteworthy (since XWiki 7.1 Milestone 1) =
10 10  
... ... @@ -30,24 +30,21 @@
30 30  
31 31  {{image reference="elapsedtimetree.png"/}}
32 32  
33 -== Miscellaneous ==
34 34  
35 -* Mail API has been slightly modified to fix a bug when waiting for all mails to have been processed (the ##waitForProcessing()## wasn't really waiting!). As a consequence calls to ##MailResult.waitTillProcessed(long timeout)## and ##MailResult.isProcessed()## have been replaced by calls to ##MailStatusResult.waitTillProcessed(long timeout)## and ##MailStatusResult.isProcessed()##. Note that for backward compatibility reason the scripting API still supports the old API (but it's deprecated and you should move your code to use the new API).
36 -
37 -* Mail Status Store API has been refactored to provides ordered result based on any status fields. A new method also ease loading a single status for a given messageId.
38 -
39 39  See the [[full list of JIRA issues>>http://jira.xwiki.org/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+in+%28XCOMMONS%2C+XRENDERING%2C+XWIKI%2C+XE%29+and+status+%3D+Closed+and+resolution+%3D+Fixed+and+fixVersion+%3D+%22<version>%22&tempMax=1000]] fixed in this release.
40 40  
41 41  = For Developers =
42 42  
43 -== Mail API: Send prepared mime message to multiple users as independent message ==
38 +== Mail API improvements ==
44 44  
45 -A new mime message cloning factory (hint "message") is available to be used with iterator factories. It duplicates a given source message as is, to allow sending it to multiple users as independent messages. See [[Example 5>>extensions:Extension.Mail Sender API||anchor="HExample5:SendapreparedmimemessagetoalistofUsersandGroups"]] of the documentation for a sample.
40 +* Send prepared mime message to multiple users as independent message. A new mime message cloning factory (hint "message") is available to be used with iterator factories. It duplicates a given source message as is, to allow sending it to multiple users as independent messages. See [[Example 5>>extensions:Extension.Mail Sender API||anchor="HExample5:SendapreparedmimemessagetoalistofUsersandGroups"]] of the documentation for a sample.
46 46  
47 -== Deprecated and Retired projects ==
42 +* Mail API has been slightly modified to fix a bug when waiting for all mails to have been processed (the ##waitForProcessing()## wasn't really waiting!). As a consequence calls to ##MailResult.waitTillProcessed(long timeout)## and ##MailResult.isProcessed()## have been replaced by calls to ##MailStatusResult.waitTillProcessed(long timeout)## and ##MailStatusResult.isProcessed()##. Note that for backward compatibility reason the scripting API still supports the old API (but it's deprecated and you should move your code to use the new API).
48 48  
49 -<description of deprecated and retired projects>
44 +* Mail Status Store API has been refactored to provides ordered result based on any status fields. A new method also ease loading a single status for a given messageId.
50 50  
46 +* The Mail module's prepare step now does a better handling of the ExecutionContext by cloning it. This way you can safely use it while rendering your mail's template, when you are using the velocity bindings. More details on [[XWIKI-12090>>http://jira.xwiki.org/browse/XWIKI-12090]]
47 +
51 51  == Job progress improvements ==
52 52  
53 53  It's now possible to associate message to each step of the progress. Also a new API have been added to make easier to notify about progress in scripts.
... ... @@ -60,27 +60,18 @@
60 60  The following dependencies have been upgraded:
61 61  
62 62  * [[Less4j 1.11.0>>http://jira.xwiki.org/browse/XWIKI-12000]]
60 +* [[Infinispan 7.2.1>>http://jira.xwiki.org/browse/XWIKI-12097]]
63 63  
64 -== Miscellaneous ==
65 -
66 -* The Mail module's prepare step now does a better handling of the ExecutionContext by cloning it. This way you can safely use it while rendering your mail's template, when you are using the velocity bindings. More details on [[XWIKI-12090>>http://jira.xwiki.org/browse/XWIKI-12090]]
67 -
68 68  = Translations =
69 69  
70 70  The following translations have been updated:
71 71  
72 -{{language codes="none, none"/}}
66 +{{language codes="fr"/}}
73 73  
74 74  = Tested Browsers & Databases =
75 75  
76 76  {{include reference="TestReports.ManualTestReportTemplateSummary"/}}
77 77  
78 -= Performances tests compared to <last super stable version> =
79 -
80 -<a summary of the comparison with latest super stable version>
81 -
82 -More details on <link to the test report>.
83 -
84 84  = Known issues =
85 85  
86 86  * [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]]
... ... @@ -91,10 +91,6 @@
91 91  
92 92  When upgrading make sure you compare your ##xwiki.cfg##, ##xwiki.properties## and ##web.xml## files with the newest version since some configuration parameters may have been modified or added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.
93 93  
94 -== Issues specific to XWiki <version> ==
95 -
96 -<issues specific to the project>
97 -
98 98  == API Breakages ==
99 99  
100 100  The following APIs were modified since <project> <version - 1>:

Get Connected