Review main Merged

6167[TASK] Update information in NEWS.txt

Xavier Perseguers CR +2 V +2 Hard +309 −83 updated 06/03/13, 20:49

Commit message

File NEWS.txt should reflect latest changes in TYPO3 4.6.

Review

  • Code review CR +2
    • Xavier Perseguers +2
  • Verified V +2
    • Xavier Perseguers +2

Issues 1

Files 1

Review log 21

  1. Xavier Perseguers commented on patch set 1 10/23/11, 18:26

    Do not submit Patch is not ready (missing Extbase/Fluid info at least) but open for comments. Information is based on http://wiki.typo3.org/TYPO3_4.6
  2. Xavier Perseguers commented on patch set 1 10/23/11, 18:26

    (29 inline comments) Thanks for your senseful comments
  3. Xavier Perseguers uploaded patch set 2 10/23/11, 18:26

  4. Xavier Perseguers commented on patch set 2 10/23/11, 18:26

    No score
  5. Xavier Perseguers uploaded patch set 3 10/23/11, 18:26

  6. Xavier Perseguers uploaded patch set 4 10/23/11, 18:26

  7. Xavier Perseguers uploaded patch set 5 10/23/11, 18:26

  8. Xavier Perseguers uploaded patch set 6 10/23/11, 18:26

  9. Xavier Perseguers uploaded patch set 7 10/23/11, 18:26

  10. Steffen Gebert commented on patch set 1 10/23/11, 18:26

    (1 inline comment)

    NEWS.txt:8

    would prefer "in-depth", although both versions should be possible

    NEWS.txt:14

    I really miss a "Deprecated methods have been removed... " here.

    NEWS.txt:34

    Uppercase Improvements, as you're in a headline

    NEWS.txt:34

    change, if an extension

    NEWS.txt:46

    What about moving this to the Compatibiltiy section above?

    NEWS.txt:51

    for localization files

    NEWS.txt:52

    Translation Server

    NEWS.txt:54

    Translation Server

    NEWS.txt:61

    remove trailing ,

    NEWS.txt:65

    default (English)

    NEWS.txt:73

    Scheduler

    NEWS.txt:75

    Scheduler

    NEWS.txt:77

    should be => have to be updated (IIRC it's kond of breaking change, isn't it?)

    NEWS.txt:86

    I still wonder, why this is a so called "project".. what about "The new Form content element"

    NEWS.txt:90

    IMHO exactly, how

    NEWS.txt:100

    project.. (if you change it above, too)

    NEWS.txt:101

    Introduction Package

    NEWS.txt:104

    Loading the new Form system extension..

    NEWS.txt:128

    We could add here: * On-the-fly minification of inline JavaScript code disabled The use of the JSmin library, which previously minified the inline JavaScript code in the Backend was dropped. Due to its immense performance impact, editors benefit from faster response times, while the increase of the output is only of negligible order.

    NEWS.txt:195

    obsolesced is no word ;)

    NEWS.txt:195 Reply

    Damn it.. dict.cc seems to be incomplete then ;-)

    NEWS.txt:212

    * Caching Framework now mandatory

    NEWS.txt:214

    Caching Framework

    NEWS.txt:215

    was removed

    NEWS.txt:220

    Framework: DB Backend

    NEWS.txt:222

    Database Backend

    NEWS.txt:224

    Caching Framework

    NEWS.txt:254

    I thought locallang is dead ^^

    NEWS.txt:277

    (all algorithms available by PHP function ..?)

    NEWS.txt:299

    This change could be moved way up in this file. Maybe mention also that a broken OpenSSL configuration could be responsible, in case of logins are impossible (although this should not happen anymore..). And the information is a bit wrong: It is not used automatically! Only new installations. Upgrading users are strongly advised to manually enable it blabla.
  11. Steffen Gebert commented on patch set 1 10/23/11, 18:26

    (29 inline comments) Just read once through it. Maybe it's only my opinion, but still using "Form project" as an official name sounds a bit weird for me. For TYPO3 users it's just the new Form content element (or system extension).
  12. Steffen Gebert commented on patch set 4 10/23/11, 18:26

    Thanks for your corrections, Xavier! What came to my mind is the new per-minute caching lifetime, which is not mentioned, yet.
  13. Mr. Jenkins commented on patch set 1 10/23/11, 18:26

  14. Mr. Jenkins commented on patch set 2 10/23/11, 18:26

  15. Mr. Jenkins commented on patch set 3 10/23/11, 18:26

  16. Mr. Jenkins commented on patch set 4 10/23/11, 18:26

  17. Mr. Jenkins commented on patch set 5 10/23/11, 18:26

  18. Mr. Jenkins commented on patch set 6 10/23/11, 18:26

  19. Mr. Jenkins commented on patch set 7 10/23/11, 18:26

  20. Xavier Perseguers commented on patch set 7 V 0 10/23/11, 18:26

    by team member; Looks good to me, approved
  21. Xavier Perseguers merged patch set 7 10/23/11, 18:26