TYPO3 CMS 6.2 LTS beta6 released

What happened since beta5?

Notable improvements

• Flush opcode caches while saving PHP files (<link http: forge.typo3.org issues _top>#55252, <link http: forge.typo3.org issues _top>#56546, <link http: forge.typo3.org issues _top>#56554). This should fix the problem with PHP 5.5 and the opcache (i.e. in the Install Tool) as mentioned in the beta5 release notes. Please test this new feature if it works as expected in your environment!
• TYPO3 now only sets a frontend user cookie (fe_session) if there is session data or the user is logged in (<link http: forge.typo3.org issues _top>#55549, <link http: forge.typo3.org issues _top>#55845). This minimizes traffic, allows better optimization of reverse proxies (i.e. varnish). It also obsoletes the setting "dontSetCookie". Read more about it in the NEWS.md file.
• css_styled_content is now selected to be installed in a new empty installation by default (<link http: forge.typo3.org issues _top>#56292).
• tt_content "categories" field is now an exclude field, so it can be disabled for editors (<link http: forge.typo3.org issues _top>#53454).

Third party library updates

• Updated normalize.css to version 3.0.0 (<link http: forge.typo3.org issues _top>#55316).
• Updated Swift Mailer to 5.0.3 (<link http: forge.typo3.org issues _top>#55745).

Package Management / Extension Manager

• Benni worked out a more robust solution of adding plugins to content rendering TypoScript (<link http: forge.typo3.org issues _top>#55942). This basically fixes the issues with extension plugins not working in the frontend due to the TypoScript not being present (i.e. indexed search <link http: forge.typo3.org issues _top>#55174, felogin <link http: forge.typo3.org issues _top>#55557), depending on the loading order of the extensions. We didn't want to make indexed search or felogin dependant of css_styled_content.
• Improved handling of the TYPO3 version which was making it impossible to install extensions compatible with "6.2.0" in a beta release (<link http: forge.typo3.org issues _top>#23902).
• The composer names of the system extensions were changed from "typo3/cms/*" to "typo3/cms-*" to be standards compliant (<link http: forge.typo3.org issues _top>#53753). See the Upgrade Notes on how to deal with this change if you are upgrading from a previous beta.
• Extension Manager performance: Speed up updating the extension list by improving some SQL indexes (<link http: forge.typo3.org issues _top>#56354) and by doing more intelligent queries (<link http: forge.typo3.org issues _top>#55820). Great improvement by Jost Baron: Thanks!
• Fixed Extension Upload ending with a PHP Error (<link http: forge.typo3.org issues _top>#53210).

Install Tool and Upgrade Wizards

Upgrade Wizards We worked on streamlining and optimizing the Upgrade Wizards, which will be important for many of you upgrading from 4.5 (or later versions) to 6.2. Please give them a new try now!

• There are now two Wizards surrounding all other Upgrade Wizards to update the database schema (SQL) (<link http: forge.typo3.org issues _top>#53890): One creates new fields and tables at the start, the other applies required changes at the end. This now makes it possible to do the whole Upgrade process without switching between "Database Analyser" and "Upgrade Wizard". Just as we recommend it, using only the Upgrade Wizard! Great achievement brought to us by Stephan Großberndt!
• File Abstraction Layer Upgrade Wizards: The TCA-FAL migration for tt_content (<link http: forge.typo3.org issues _top>#53845, <link http: forge.typo3.org issues _top>#53891), the RTE Magic Image FAL migration wizard (<link http: forge.typo3.org issues _top>#53846) and the Wizard for migrating FAL references (<link http: forge.typo3.org issues _top>#53650) were all enhanced.
• "Update Wizard" was renamed to "Upgrade Wizard" (<link http: forge.typo3.org issues _top>#55970).
• Removed outdated Wizards (<link http: forge.typo3.org issues _top>#54930).

Install Tool

• The menu items of the Install Tool were reordered for better usability (<link http: forge.typo3.org issues _top>#56497).
• Install Tool has a new check for correct system locale settings (<link http: forge.typo3.org issues _top>#55721). Great contribution by new contributor Zbigniew Jacko, thanks!

Performance

Our favorite topic "Performance" got yet more attention in the area of micro-optimization and general improvements since beta5. We will now try to focus on bigger aspects (i.e. the class loader and alias and it's caching, package management). There are some WIP patches already pending in these areas, and there is a list created by Steffen Ritter with some findings (<link http: forge.typo3.org issues _top>#56307). Start your profiler on your site, benchmark and bring us your findings and improvement ideas! The "intval to (int)" patch which was included in beta5 (<link http: forge.typo3.org issues _top>#54265) broke some things, which are all solved. I.e. the levelmedia was not working correctly (<link http: forge.typo3.org issues _top>#55706), pagetype was not respected in page cache (<link http: forge.typo3.org issues _top>#55753) and there were some other regressions in ternaries discovered and fixed along the way (<link http: forge.typo3.org issues _top>#55923). Opening Web>List on a page with many large tables was improved with a SQL change (<link http: forge.typo3.org issues _top>#55891). Performance improvements were added in GeneralUtility::getFilesInDir() (<link http: forge.typo3.org issues _top>#54095), which is now covered with unit tests to validate the optimizations (<link http: forge.typo3.org issues _top>#55762, <link http: forge.typo3.org issues _top>#55871, <link http: forge.typo3.org issues _top>#55864, <link http: forge.typo3.org issues _top>#56121). We also improved performance of the GeneralUtility::revExplode method (<link http: forge.typo3.org issues _top>#55564) and fixed some regressions found after merging this solution (<link http: forge.typo3.org issues _top>#55838, <link http: forge.typo3.org issues _top>#56405). Optimized GeneralUtility::trimExplode() (<link http: forge.typo3.org issues _top>#55198), \TYPO3\CMS\Lang\LanguageService (<link http: forge.typo3.org issues _top>#56109), GeneralUtility::rmFromList (<link http: forge.typo3.org issues _top>#53677), isPackageActive() (<link http: forge.typo3.org issues _top>#55749), heavily used path methods in GeneralUtility (<link http: forge.typo3.org issues _top>#54525) and ArrayUtility::sortArraysByKey() (<link http: forge.typo3.org issues _top>#55899). Reduced redundant calls to getClassSchema() in DataMapper::thawProperties() (<link http: forge.typo3.org issues _top>#55991). We now use PHP native htmlspecialchars_decode() when possible (<link http: forge.typo3.org issues _top>#54777). And we use stat() instead of filemtime + filesize (<link http: forge.typo3.org issues _top>#55574). Kudos for the tremenduous work done by Michiel Roos on lots of these issues!

Security / CSRF protection

Helmut did a great job together with Alexander Schnitzler in improving CSRF protection of our backend, which was already announced in <link http: typo3.org news article cross-site-request-forgery-protection-in-typo3-cms-62>this public news. Many pieces of this work were already merged in beta6. This also lead to improved usability of session logouts when working with multiple tabs open (<link http: forge.typo3.org issues _top>#56453). This is especially important now that the CSRF tokens are validated virtually everywhere in the backend. One goal was to reduce the amount of entry scripts to the system, to make sure we have more control over the process. Some preparation work: Switch info and func module to mod dispatcher (<link http: forge.typo3.org issues _top>#55672, <link http: forge.typo3.org issues _top>#55670, <link http: forge.typo3.org issues _top>#55809). Cleanup ext:frontend web_info module routing (<link http: forge.typo3.org issues _top>#55797), form sysext entry script cleanup (<link http: forge.typo3.org issues _top>#55669), making sure M parameter is first in URL (<link http: forge.typo3.org issues _top>#56404). Then came the main part, which in parts are breaking changes:

• Added CSRF protection to mod.php (<link http: forge.typo3.org issues _top>#55509).
• Added CSRF Protection for tce_file.php (<link http: forge.typo3.org issues _top>#55515).
• Added API to CSRF protect Ajax calls in Backend (<link http: forge.typo3.org issues _top>#56345).
• Protect core Ajax calls against CSRF (<link http: forge.typo3.org issues _top>#56356).
• Added a new way to register a TCA wizards (<link http: forge.typo3.org issues _top>#56268). This will be documented as it's finished here: <link http: forge.typo3.org issues _top>#56279.
• Removed old wizard scripts (<link http: forge.typo3.org issues _top>#56454)

We used the new way to register the wizards: colorpicker (<link http: forge.typo3.org issues _top>#56436), rte (<link http: forge.typo3.org issues _top>#56437), forms (<link http: forge.typo3.org issues _top>#56438), table (<link http: forge.typo3.org issues _top>#56435), list (<link http: forge.typo3.org issues _top>#56434), edit (<link http: forge.typo3.org issues _top>#56272), add (<link http: forge.typo3.org issues _top>#56432) and backend_layout (<link http: forge.typo3.org issues _top>#56471). Some fixes were incorporated as they popped up: Fix Redirect after switch-to-user (<link http: forge.typo3.org issues _top>#56364). Fix module access regressions (<link http: forge.typo3.org issues _top>#56359, <link http: forge.typo3.org issues _top>#56375). Do not save failed token messages in session (<link http: forge.typo3.org issues _top>#56357). Initialize FormProtectionFactory later in alt_doc.php (<link http: forge.typo3.org issues _top>#55856).

API

• We've added two Signals in EditDocumentController after init (<link http: forge.typo3.org issues _top>#56381) and after preInit (<link http: forge.typo3.org issues _top>#56195). This will be used for example by gridelements.
• DatabaseConnection (TYPO3_DB) now has a central method where all queries go through (<link http: forge.typo3.org issues _top>#55769)

Extbase

• If you register backend modules using ExtensionUtility::registerModule, you can now omit the parameter $controllerActions if it's just an empty array (<link http: forge.typo3.org issues _top>#54869).
• Many calls inside the persistence layer (Typo3DbBackend) now use proper API of the DatabaseConnection (<link http: forge.typo3.org issues _top>#55571). This is part of a yet not finished ongoing effort to make the Extbase persistence faster (see also <link http: forge.typo3.org issues _top>#55360 and <link http: forge.typo3.org issues _top>#55167).
• Since beta5 (<link http: forge.typo3.org issues _top>#55569), flexform data was not loaded anymore in Extbase plugins. This was solved in <link http: forge.typo3.org issues _top>#55687.

Fluid

• A fallback "default" case was added to the SwitchViewhelper to make it complete (<link http: forge.typo3.org issues _top>#49371).
• Breaking change: f:format.date formats the date to system default (<link http: forge.typo3.org issues _top>#55790).

Frontend and TypoScript

• Minor breaking change: In alpha1 we've added a categories-based menu. The TypoScript "tt_content.menu.20.9" was renamed to the more speaking "tt_content.menu.20.categorized_pages" (<link http: forge.typo3.org issues _top>#54611). If you have already used that in your templates, you need to adapt it.
• Added CSS libs functionality for page renderer - like we already had for JS libs - to be included before any other CSS (<link http: forge.typo3.org issues _top>#55474). Can be used in TypoScript with the page.includeCSSLibs setting.
• Content Element "Table" did not allow multiple css classes like "class1 class": now it does (<link http: forge.typo3.org issues _top>#55470).

RTE

• Stan made the RTE Link Wizard (<link http: forge.typo3.org issues _top>#55951) and Image Wizard (<link http: forge.typo3.org issues _top>#55946) styling more consistent.
• Fixed buggy folder tree icons in the RTE Image Wizard (<link http: forge.typo3.org issues _top>#53259).
• Make the RTE work in frontend again (<link http: forge.typo3.org issues _top>#56027) and fixed a compatibility between ExtJS 3.4.1 and IE 11+ (<link http: forge.typo3.org issues _top>#56192).

Backend User Interface

• Added mapping between file extensions .pps, .ppsx to powerpoint icon (<link http: forge.typo3.org issues _top>#53833).
• Button style :active and :hover (<link http: forge.typo3.org issues _top>#56480).
• Unify UL/OL standard (<link http: forge.typo3.org issues _top>#55819) and .list-unstyled for ol & ul (<link http: forge.typo3.org issues _top>#55834, <link http: forge.typo3.org issues _top>#56062).
• File>List: use t3-table & semantic HTML in localization (<link http: forge.typo3.org issues _top>#55810, <link http: forge.typo3.org issues _top>#56020).
• Web>List: use t3-table & tree sprites (AbstractTreeView) (<link http: forge.typo3.org issues _top>#55784).
• EXT: tstemplate - use treeline sprite icons (<link http: forge.typo3.org issues _top>#56229).
• Forms: Input/textarea :focus style (<link http: forge.typo3.org issues _top>#55901).
• Fixed the bug when adding new image to content element broke the layout (<link http: forge.typo3.org issues _top>#56018).
• Scheduler: Added (>) icon to execute button (<link http: forge.typo3.org issues _top>#55789).

File Abstraction Layer

Improvements

• FAL functions are now used for css_styled_image textpic rendering (<link http: forge.typo3.org issues _top>#53764).
• RTE MagicImage should use FAL processing API (<link http: forge.typo3.org issues _top>#51807).
• Added a FileCollectionRegistry, allowing other types of "file collections" to be registerd, a feature enabling extensions to provide DAM like selections (<link http: forge.typo3.org issues _top>#53910).
• The drag+drop dialog is now disabled if the FAL driver is set to readonly (<link http: forge.typo3.org issues _top>#56443).
• In beta5 we introduced the concept of a "default storage" (only one can be set). The new TCA setting "maximumRecordsChecked" allowed only one storage to be set as default. But the usability was not good, as the user got no information that the checkbox could not be set. This alert was now added in beta6 (<link http: forge.typo3.org issues _top>#55590).
• Added IconUtility::getSpriteIconForResource() which also provides a hook for extensions to manipulate the icons based on whatever they like (<link http: forge.typo3.org issues _top>#56211).

Several fixes:

• Fix a fatal error in the inline "upload" functionality for editors (<link http: forge.typo3.org issues _top>#55628).
• Fix StorageRepository::findByStorageType (<link http: forge.typo3.org issues _top>#56400).
• Respect all filemounts in file collection (<link http: forge.typo3.org issues _top>#55414).
• Update file type on mimetype change (<link http: forge.typo3.org issues _top>#54305).
• Indexer does not update the FileObjects (<link http: forge.typo3.org issues _top>#53772).
• Load file meta data properties before return (<link http: forge.typo3.org issues _top>#56035).
• StorageRepository fails to load storages (<link http: forge.typo3.org issues _top>#55992).
• Prevent double slash in isWithin check (<link http: forge.typo3.org issues _top>#55740).
• FAL links in RTE not transformed when link has rel attribute (<link http: forge.typo3.org issues _top>#54944).
• RTE Linking with file upload fails when no folder is selected (<link http: forge.typo3.org issues _top>#48512).
• Pass path instead of object to fileExistsInFolder (<link http: forge.typo3.org issues _top>#55763).
• Make FileExtensionFilter case insensitive (<link http: forge.typo3.org issues _top>#55359, <link http: forge.typo3.org issues _top>#55614).
• Filename sorting in filelist was broken (<link http: forge.typo3.org issues _top>#56128).
• Using files in eID resulted in fatal error (<link http: forge.typo3.org issues _top>#54232).
• Ignore empty inputs when creating new folders (<link http: forge.typo3.org issues _top>#56034).

Workspaces / IRRE / DataHandler fix Workpackage

Olly is working hard on the DataHandler. In preparation, a framework for frontend rendering functional tests was created (<link http: forge.typo3.org issues _top>#55882) and the DataHandler functional tests were streamlined (<link http: forge.typo3.org issues _top>#56029). Then the DataHandler IRRE functional tests were extended with many more situations (<link http: forge.typo3.org issues _top>#56072). Olly integrated and optimized the IRRE CSV Functional Tests (<link http: forge.typo3.org issues _top>#56132, <link http: forge.typo3.org issues _top>#56143, <link http: forge.typo3.org issues _top>#56161, <link http: forge.typo3.org issues _top>#56244, <link http: forge.typo3.org issues _top>#56177). After that, a set of functional test cases were added to DataHandler (workspace) (<link http: forge.typo3.org issues _top>#55563) and some more: for discarding created elements (<link http: forge.typo3.org issues _top>#56179), frontend rendering (<link http: forge.typo3.org issues _top>#56104), discarding vs. deleting workspace changes (<link http: forge.typo3.org issues _top>#56111). A bug with moving content records to a different page and change sorting was fixed (<link http: forge.typo3.org issues _top>#55573). To fix a bug when copying or localizing sys_categories, we introduced a new TCA feature, MM_oppositeUsage property (<link http: forge.typo3.org issues _top>#56061, <link http: forge.typo3.org issues _top>#56122). This will be documented in the TCA reference (https://review.typo3.org/#/c/27918/).

Testing Framework

Also our testing framework (unit and functional testing) was improved:

• Use absolute path to check for extensions (<link http: forge.typo3.org issues _top>#56204).
• Add additional configuration for functional tests (<link http: forge.typo3.org issues _top>#56187).
• Use environment variable for functional test bootstrap (<link http: forge.typo3.org issues _top>#56182).
• Use Backend User fixture for DataHandler tests (<link http: forge.typo3.org issues _top>#56070).
• Reduce memory footprint of unit tests (<link http: forge.typo3.org issues _top>#55850).

Importer / Exporter Workpackage

Marc-Bastian Heinrich also got some tasks completed from the job of making the Importer / Exporter work with relations and FAL. The basis are the test cases:

• Avoid to get a file object with the uid zero (<link http: forge.typo3.org issues _top>#55530).
• Limit the exported record fields in impexp (<link http: forge.typo3.org issues _top>#55625).
• Use DataHandler testing framework for simple import test (<link http: forge.typo3.org issues _top>#55664).
• Remove class loader in functional test tear down (<link http: forge.typo3.org issues _top>#56086).
• Extend functional tests with linked paths (<link http: forge.typo3.org issues _top>#55111).

Package Management / Class Loader / Cache

• Cache non existing classes (<link http: forge.typo3.org issues _top>#53962).
• Class Loader optimisation (<link http: forge.typo3.org issues _top>#55037).
• Class loader: avoid loading classes multiple times (<link http: forge.typo3.org issues _top>#55904).
• Allow multiple aliases for a class (<link http: forge.typo3.org issues _top>#55897).
• Fix fatal errors upon package installation (<link http: forge.typo3.org issues _top>#53795).

DBAL

New contributor Andreas Fernandez fixed a bug in that the Install Tool fatals with Oracle databases (<link http: forge.typo3.org issues _top>#56253) and a bug where quoteFieldNames() returned an empty string (<link http: forge.typo3.org issues _top>#56306). Great work! There is still an ongoing work in progress to stabilize the DBAL extension with the current 6.2 release. Xavier is active and we have gained some awareness of the pending problems, so we expect it to be rock stable until final release!

Cleanups

Some removals:

• Removed security_level option from Authentications, deprecated since 4.7 (<link http: forge.typo3.org issues _top>#56256).
• Tymek removed some empty classes implementing AbstractTreeView (<link http: forge.typo3.org issues _top>#55847) and renamed classes with the same name "localPageTree" (<link http: forge.typo3.org issues _top>#55876). The goal is to cleanup the treeView implementation mess (or at least make it less messy), see <link http: forge.typo3.org issues _top>#55830. Make sure you are not using any of these classes in your extensions, as this is a breaking change (documented in NEWS.md).
• Removed rollover (.RO) functionality from TMENU (<link http: forge.typo3.org issues _top>#55751).
• Removed some leftovers from the ancient "condensed mode" backend configuration (<link http: forge.typo3.org issues _top>#56479).
• Removed old class files from ext:openid (<link http: forge.typo3.org issues _top>#55808), ext:recycler (<link http: forge.typo3.org issues _top>#55804), ext:t3editor (<link http: forge.typo3.org issues _top>#55792).
• Remove outdated $CLIENT[FORMSTYLE] (<link http: forge.typo3.org issues _top>#56254).

Other cleanups:

• ContentObject instances are not reused anymore (it used to be a pseudo-singleton) (<link http: forge.typo3.org issues _top>#55941).
• Cleanups and fixes in the ElementBrowser (<link http: forge.typo3.org issues _top>#56406, <link http: forge.typo3.org issues _top>#56289, <link http: forge.typo3.org issues _top>#55985, <link http: forge.typo3.org issues _top>#55765 and <link http: forge.typo3.org issues _top>#55939).
• Moved TCEForms JS Code to external file - part 1 (<link http: forge.typo3.org issues _top>#46357, <link http: forge.typo3.org issues _top>#56221).
• Replaced JscharCode() with GeneralUtility::quoteJSvalue() (<link http: forge.typo3.org issues _top>#55009).
• There were some duplicated Exception codes (unix timestamps) in our codebase, which were cleaned up in <link http: forge.typo3.org issues _top>#52294. Thanks Przemyslaw Krukowski for the help!
• Improved compatibility with PHP Strict Standards in the Core API (<link http: forge.typo3.org issues _top>#47983).

Other important fixes:

• Issues with the optimizations in addToAllTCAtypes from beta5 were fixed (<link http: forge.typo3.org issues _top>#55932, <link http: forge.typo3.org issues _top>#56080).
• Adding new records in edit mode was broken since beta4: Fixed (<link http: forge.typo3.org issues _top>#56248)!
• The new responsive sourceCollection width not usable out of the box, and this was fixed (<link http: forge.typo3.org issues _top>#53169). Great first time contribution to the Core by Pascal Hinz!
• Fixed several PHP warnings in the frontend when logging out, in, submitting forms etc (<link http: forge.typo3.org issues _top>#55696, <link http: forge.typo3.org issues _top>#56508, <link http: forge.typo3.org issues _top>#55434, <link http: forge.typo3.org issues _top>#56508)
• Package Management: Fixed a Fatal error when adding composer packages to Packages folder in site root (<link http: forge.typo3.org issues _top>#55754).
• Fixed error "<link http: forge.typo3.org issues _top>#1361915596: The array $GLOBALS['TYPO3_LOADED_EXT'] may not be modified" in the configuration module (<link http: forge.typo3.org issues _top>#54449)
• Spelling of namespace \TYPO3\CMS\Tstemplate was corrected, which fixes a problem in links between TSOB and Template Analyzer (<link http: forge.typo3.org issues _top>#55764).

Downloading and Upgrading

If you have tried some earlier snapshot of the 6.2 development branch (i.e. some alpha or beta) here are some tips when upgrading to this latest beta:

• Download 6.2 beta6 from the <link>Download Page.
• Uncompress into your old Document Root.
• Switch the typo3_src symlink to the new package
• Use the Install Tool:
  • "Important Actions" and delete the whole cache content (make sure this deletes the whole typo3temp/Caches/* files and also the content of Extbase Reflection Caches - do it manually if not working otherwise!)
  • "Upgrade Wizards": Walk through all Upgrade Wizards

Additional note in beta6: The composer names of the system extensions were changed to be standards compliant (<link http: forge.typo3.org issues _top>#53753). This means that your PackageStates.php needs to be reconstructed in case you tried a previous beta. After clearing typo3temp/Cache, make sure you deactivate and activate some extension in the extension manager in order to have the PackageStates file rewritten. Keep in mind that the exact same steps are required when upgrading from a previous version of TYPO3. Note that you might need to upgrade the extensions to the latest state before upgrading the Core!

MD5 sum of packages

3617dab77b15491a596cf4cfbbf70234 typo3_src-6.2.0beta6.tar.gz 15d4f93645877a7c23695c3f41174d6f typo3_src-6.2.0beta6.zip 

Found a bug? Report it!

If you try out the beta and find some bug or issue with it, don't hesitate to report back to us. Our issue tracking system is <link http: forge.typo3.org projects typo3cms-core issues>Forge. To fill in a report, you must register as an user on typo3.org first. Then Login on Forge. Take a look at other reports as those linked in this release notes. Make sure to do a search first to see if there is already a report of the issue you have, before reporting the issue again. Do that by adding a filter "Subject" to the issue tracking filtering system or by using the "Search:" field on the top corner. If you are reporting some new issue, make sure you fill in all required fields:

• A speaking and concise subject briefly describing the problem (a phrase like "I just found a bug in TYPO3!" is not descriptive enough!)
• TYPO3 Version: specify the release of TYPO3 where the problem occurs: "6.2" in case you are trying this beta.
• Category: Try to find a matching category, it helps us filter the issue. In case of doubt which category to use, just leave it blank.
• In the text part of the issue, try to describe exactly what the problem is. A part with "How to reproduce" helps the developers understanding when the bug appears exactly.

You might want to join IRC on Freenode, channel #typo3-cms and get our attention on your bug or if you have questions if what you found is indeed a bug or some misconfiguration.

What's next?

Our next meet-up will be the <link http: wiki.typo3.org cms_codesprint_2014>Code Sprint in Venlo / Netherland from 10th to 12th of March. This will be the last code sprint before the final release. If it turns out necessary, we have the option to release a new beta7 at 13th of March right after the Code Sprint. This will then be the final Beta-Release. The week after that, we will have a Release Candidate (either Tuesday or Thursday). And then finally, at 25th of March, the long waited 6.2.0 first stable release! I can't wait for it, can you? Let's get it on!