**TYPO3 25th 4.7 Release Team Meeting - April2h 2012** **Attendants**: * Benni, Ernesto, Oliver * Offene Probleme 4.7 * SWF Object cannot render "swf-files" anymore (without video-js and <video> wrapper) * --> recreate old SWFObject * --> make new video Object "own" Element * Vorbereitung DevDays * Start 10 Uhr Dienstag * FAL Sessions fehlen noch, FAL Review Session + evtl. Vorstellung bei CoreDevs * bis inkl. Donnerstag morgen. * RC1 Releases for Backport-Branches 4.5 / 4.6 * post-pone again * missing rights for Ernesto and Xavier to directly push to backport branches * around 4.7 release we will backport new hooks to 4.5 and 4.6 --> define what especially has to be in there at the DevDays * backport releases will be a "one-time" thing * agreed to postpone until end of May (after 4.7.0 release) ====================================================================================================== **TYPO3 14th 4.7 Release Team Meeting - March 19th 2012** Tell People about htmlmail removal and UTF8 Update script Lighbox Extension???? Put Question about Migration to the Release notes...n **TYPO3 13th 4.7 Release Team Meeting - March 19th 2012** Attendants: Xavier, Benni, Olly * **TYPO3 4.7 Topics** * Check migration/upgrade wizards * HTML5 per default * is temporarily abandoned for 4.7 since Patrick Broens (as developer of that feature during the BLE phase) had valid concerns * still needs to be checked what that means in detail - the HTML5 feature is still available, but currently not suggested to be the TYPO3 default behavior * UTF-8 per default * initDB, forceRenderCharset, metaCharset (FE) * lookup whether all tables are in UTF-8 mode * maybe binary check * Jigal has a converter script which is doing analysis and converts data (however this one shall not be shipped with the core - instead we can imagine to put it to ter TER) * in general we should make use of the exception codes that are redirected to the wiki - there more details on upgrading and the procedure will be provided * **TYPO3 4.6 \& 4.5 - fixing the regression-regression-fixes...** * fixed \url{http://forge.typo3.org/issues/34662} (Fatal Error Deprecation Log) * modified \url{http://forge.typo3.org/issues/30892} \& \url{http://forge.typo3.org/issues/34698} -> pending \url{http://forge.typo3.org/issues/34820} (Preview Domain) * example of the current implementation * Backend URL \url{https://backend.mydomain.com:8081/typo3/} * FRONTEND: \url{http://www.mydomain.com/index.php?id=123} * EXPECTED for some cases but not all: (expected \url{https://backend...:8081/index.php?id=123)} * Problem: sometimes only /typo3/ may be used in "Frontend" => "/index.php" does not work! * General behaviour: sys\_domain takes precedence over Backend URL * needs feedback \url{http://forge.typo3.org/issues/34835} (Fatal Error with Preview Domain - could be reproduced) * The reproducible bugs are fixed in the accordant branches, thus we will provide a buzz article explaining the behaviour and how the patch can be applied locally, out of the Gerrit review * Thus, there won't be a dedicated release this week just to fix the regressions - the fixed will be part of the next regular maintainance releases * **General LTS Strategy** * The main reason for 4.5 being a LTS was to still be compable with PHP 5.2 and IE6 in the backend * in between support for PHP 5.2 has been discontinued by PHP and also by most distributors * Besides that our 6-monthly release cycle forder agencies to upgrade to the next version very often and also was an argument to have a LTS release * However, the period of 3 years seems to too long in general - so TYPO3 4.5 LTS will be supported until 2014 (sure!), but the next LTS version might only be valid for e.g. 18-24 months * The whole topic shall be discussed by the community - during T3DD12 there shall be a decision * **Backport-Branches** * The interest of individually backporting features was rather low. * Goal is to promote latest stable releases, not the last LTS version (since performance improvements and clean-up will only be part of that latest version) * Besides that most of the requested backports depend on the overworked caching framework or are at least releated to it - which makes it quite difficult to deal with the expected backwards compatibility in an LTS version. * The whole topic also shall be discussed by (=> explained to!) the community. * **Future Development (master)** * File Abstraction Layer * Mini-Code sprint with Benni Mack, Ingmar Schlecht, Andreas Wolf in Stuttgart on March 16th-18th 2012 * getImgResource was separated into smaller functional parts -> \url{http://git.typo3.org/TYPO3v4/Incubator.git?a=blob;f=t3lib/file/Service/FileProcessingService.php;hb=plain-fileabstraction} * Stanislas is currently working on RTE integration for FAL * it's planned to recreate pathes for review.typo3.org again next week - everybody is encouraged to review and test as much as possible then --------------------------------------------------------------------------------------------------------------------------------------------------------- TYPO3** 12th 4.7 Release Team Meeting - March 12th 2012** Attendants: Xavier, Benni, Ben, Oliver, Steffen * **RC1 Releases for Backport-Branches 4.5 / 4.6** * Backport releases are post-poned since Ernesto has to leave for Brazil * Normal patch-level releases will be issued due to a smaller regression * we will review this evening to make the releases a bit more "worthy" * \url{https://review.typo3.org/#/q/status:open+project:%2522TYPO3v4/Core%2522+branch:TYPO3\_4-5+CodeReview%253E%253D1+Verified%253E%253D1+-Verified%253C%253D-1+-CodeReview%253C%253D-1,n,z} * * **eMail about the Release // press and so then** * Release Parties again will be on Tuesday * the documentation team tries to finish the documentation for the release * they report back if this is possible * Ben will remind Soren again about press releases * Ben will ask the Design team to create Banners for Release Parties as well as Stage Graphic * **Current HTML5 behaviour is not smooth** * some options contradict and the output is not really "non-xhtml" like * shortly looked and discussed option proposed in \url{https://review.typo3.org/#/c/9537/} * **Online CoreTeam Meeting will be on Thursday 15.03.2012 5pm** * will be on BigBlueButton * everyone interested is invited to listen our discussions * ========================================================================================================= TYPO3** 12th 4.7 Release Team Meeting - March 5th 2012** Attendants: Xavier, Ben, Ernesto, Oliver, Steffen, Benni * * **incompatibility Blank/Dummy to master Branch** * about/aboutmodules installed by default -- extbase/fluid not * --> **ToDo Steffen: enable extbase/fluid within the package by default** * **New features / content in Introduction Package und Gov-Package** * Workspaces demonstration should be enhanced in the Introduction Package * HTML 5 Video Stuff * revalidate all pages * think about changing tt\_news to news * remove infos about the FAL within Gov-Package * * **Extbase \& Beta3** * Due to the Extbase CodeSprint Beta 3 is reactivated * **Release Planning // ToDo: Steffen** * Release Notes in forge wiki are broken - Probably got not saved from laax * CleanUp Issue Tracker and attach Bugs to Beta2 and Beta3 - define must haves * **News Explaining the Government Package** * News what it is about * probably typo3.org/download * **Patchlevel Releases 4.5 und 4.6** * 40-50 patches pending in the branches * Releasing of patch level of 4.5 and 4.6 on March 6th 2012 * **Release Candidate Backport Branch** * next tuesday (March 13th 2012) release candidates for Backports Releases to 4.6 and 4.5 * check the announced features for backports of beeing merged * * **FAL into Core until October** * finish up the integration Tasks as soon as possible on master * if 6.0 won't be in October FAL should be released in another version * if 6.0 comes up we could Drop some backwards compat which would totally clean up the integration codebase * master to be merged back to plain-fileabstraction, finishing up the Tasks there, resulting in new patch sets for gerrit * ==================================================== TYPO3** 11th 4.7 Release Team Meeting - February 2nd 2012** Attendants: Oliver, Steffen, Xavier * Topic 1: Leadership and Motivation (an response to Jigals Mail) * Summary of his Mail: * FAL should have been a finished outcome of BLE? Why not merged when it has been announced to be finished * Why can big parts of Core Project be based of ExtjS4 if not officially announces * Communication lack even within Release-Team * Role and Todos for Release-Team? * Release-manager should not only query state, but work actively on getting things done * more actively ask people to take care of special tasks * publish lists of open issues * "Announcing that help is needed is not enough" * Facts Collected * There have been orginisational as well as communication issues * BLE project never has been to be "4.7", but a rough bases to build upon for 4.7: The feature set for a customer has been fullfilled, but not a generic solution which would have been mergable to core * projects have been kept to long in private and probable issues somehow hidden * BUT: There always have been team leaders announced to several teams, and that there is work where help is needed * quering special people as is not the main task, but communicating about problems is * open issues \& problems to be tackled * FAL not merged, yet * Problems: * Upgrade Wizards * Image-Rendering * stdWrap Backwards-COmpatibility needs to be checked * --> report them to FORGE NOW * start pushing stuff to gerrit today * allow smaller changes like new Signals/Slots which could be considered as Feature even after Beta1 * Console-Application is a stand-alone product * needs endpoint for tasks (which can be delivered as extension) * specials created in this scope won't be part of 4.7 * Media Extension * got screwed with ExtJS4 revert * not part of the Core (separate Extension, but "A-class") * needs very much TLC (= tender loving care) :) * collections by category not creatable any more since the ui is missing * new collection type or new interface for creation has to be done * state of indexing has to be checked * Youtube videos are not working with the currenten/overworked MEDIA element * adaption of Introduction Package and Government Package to newest features * database upgrades like e.g. for file abstraction layer * HTML5 video integration (we need a nice video/screencast for that!) * use "new" indexed search TYPO3** 10th 4.7 Release Team Meeting - January 30nd 2012** Attendants: Ernesto, Olli, Ingmar, Ben, Xavier and Steffen * Nothing new about 4.7 besides FAL * FAL Team is meeting in Stuttgart, * Ingmar and Olly plan pushing patches as of Wednesday * "Gremlins" handling [Mail from Olly to Ben] * community based feedback requested on annoying stuff (not only developers) * gather and sum the issues * fix them somehow (sprint?) * Ideas for promotion * article in T3N * News article (or sth. else) needed * Stage item on typo3.org * Campaign designed by designteam * Text/page in About Modules. * Links * \url{http://wiki.typo3.org/Zap\_The\_Gremlins} * \url{http://news.typo3.org/news/article/zap-the-gremlins-lets-zapem/} * \url{http://t3n.de/magazin/typo3-40-zap-gremlins-weg-storenfrieden-ghostbusters-219159/} * [**TODO Olly**] Mail to public v4-list to kick-start this project and ask for feedback/participants * Additional TASK for Backport-Branches * \url{https://review.typo3.org/#change,8764} * It's about allowing "shorter" OpenID identifier... * One month from now: BackPort-Release for 4.5 (= Feb 28th 2012, or Feb 29th - only happens every 4 years...) * announcement has to be done early * Release Candidate will be published via announce list, too * ExtJS4 Mail / ExtJS Workshop on T3DD by Ben * not one big topic the Sencha guys could solve * no solution for dealing with extensions based on extjs * we should not invest more time (4.1 beta breaks with 4.0 again, so let's wait) * workshop on T3DD does not make sense (maybe) * should become a backend technology workshop with a long-term look * Friendly Ghost Assignement status * friendly ghost calendar might be updated as there are new availibilites in doodle * Olly will take care of it * T3DD12 * list of people has been send to the organisation team * suggestion for Comfort Hotel will be done * suggestion for voucher: lower number of places to be sure Core team members may book their place, and free them in 2-3 weeks anyway... ------ * Side Info to Ben: Preparation of R\&D Team Meeting * * ----------------------------------------------------------------------------------------------- TYPO3** 9th 4.7 Release Team Meeting - January 23rd 2012** * Review of Last Weeks Todos * all "required" patches have been merged * soutNo new stuff on the "HEAD" vs "TAG" patchsout se below * "Gremlins" handling * [**TODO Olly**] Discuss that further with Ben * Merging Mailing-Lists * v4 list, core list, dev list * not much action on each of them, so maybe think about merging them to have one list for the topic "core/extension development" * --> Steffen Ritter write a mailing to the core-internal list, checking for consesus before reaching out * Process for standard release: * Create a tag (eg. 4.6.4) from the HEAD of the 4-6 branch * There is a regression => release 4.6.5 the same way * Security release (problem found in 1 month from now => 4.6.4 is already installed on websites) * sout4.6.5 = 4.6 HEAD + securitysout * sout4.6.4-sec sout * We create a TYPO3\_4-6-5 branch as clone of TYPO3\_4\_6\_4 tag (instead of HEAD TYPO3\_4-6, actually latest TAG) * apply security fixes * raise version number (corresponding to branch name) * tag it * + apply security fixes to HEAD of TYPO3\_4-6 * fixing regressions happens then in the TYPO3\_4-6-5 branch --> released as TYPO3 4.6.6 (regression fixes are security patches as well) * just requires new release type in phing script "**security**" (besides alpha, beta, rc, regular) * git cherry * TYPO3 4.6.6 (bug fixes from 4.6.4 + security fixes coming from 4.6.5) would be released something like 2-3 weeks AFTER 4.6.5 Security phing script: * - create a branch out of latest tag (security or not) * - apply "pending" security fixes (not already merged) - may be a regression fix, but in security branch ----------------------------------------------------------------------------------------------- **TYPO3 4.7 Release Team Meeting - January 16th 2012** * Alpha 3 tomorrow // Patchlevel 4.6 and 4.5 ✔ * Must haves: * Problem with "last updated" menu: \url{https://review.typo3.org/#change,7739} * Backport of md5.js replacement in TYPO3\_4-6 and TYPO3\_4-5 (\url{https://review.typo3.org/#change,5691)} and possibly TYPO3\_4-4 as announced (\url{https://review.typo3.org/#change,5692)} * **[TODO Olly]** Will analyze situation and current patches soutand take care of the releases tomorrowsout * Should Have: * pre-FAL TCA/TCEforms additions by Ingmar * Bugfix release vs Security release: * **[TODO Olly]** Investigate how to apply security fixes on top of previous bugfix release instead of "HEAD" * Roadmap changes ✔ * since postponing alpha3 was not really announced in an article, we should do that for further changes to the roadmap * besides that, a summary of the ExtJS discussion needs to be part of an announcement the next days * 3 proposals for roadmap changes around * need to agree to one, and anounce it properly * **a) Keeping the final release date, but extend alpha phase **✔ * + reduce to 2 betas and four weeks after each * + extend to 2 RCs and one week after each * + get one additional weeks to beta1 * * 2012-02-14 4.7.0 beta1 * 2012-03-13 4.7.0 beta2 * 2012-04-10 4.7.0 RC1 (as planned) * 2012-04-17 4.7.0 RC2 * 2012-04-24 4.7.0 final (as planned) * * b) Postpone the final release * + postpone beta1 by 4 weeks * + postpone final by 5 weeks * + extend to 2 RCs * * 2012-03-06 4.7.0 beta1 * 2012-03-27 4.7.0 beta2 * 2012-04-17 4.7.0 beta3 * 2012-05-08 4.7.0 RC1 * 2012-05-22 4.7.0 RC2 * 2012-05-29 4.7.0 final * * c) what about mixing both options * + move Beta 1 for 2 Weeks * + move final release for 3 weeks * + get one additional release candidate, each one week * * 2012-02-21 beta 1 * 2012-02-13 beta 2 * 2012-04-17 beta 3 * 2012-05-02 RC 1 * 2012-05-08 RC 2 * 2012-05-15 Final * * ExtJS 4 Status ✔ * ExtJS 3 got removed for TYPO3 4.7-alpha3, the future of ExtJS 4 in some of the next TYPO3 releases (such of 4.8 or 4.9) is not really decided on * currently there are some discussions to use jQuery with the possibility to run different versions of that library side-by-side (for the regular JS stuff), but still have ExtJS for widgets though * see \url{http://lists.typo3.org/pipermail/typo3-project-v4/2012-January/003231.html} * FAL Status ✔ * preview \url{https://github.com/ohader/TYPO3v4-Core/tree/fileabstraction} (will be on TYPO3 Incubator later) * filelist needed to be redone since ExtJS 4 has been dropped * Benni reworked the old Tree and File-Module to work again * media extension has no solution right now (ExtJS 4 dropping issue) * external extension * properly vidi TER ext, too * More features ✔ * Grid Elements (Joey) * Logging API (Steffen Müller and team) * T3DD12 Core Team Meeting ✔ * rather have code-sprint instead of a organisational/strategic meeting * the meeting is not for holiday, it's for getting things done and progess * maybe just one day instead of three days * maybe open the "meeting" for other active delopers as well, not only the members of the v4 Core Development Team * "Gremlins" handling (-> next meeting) ✔ * Merging Mailing-Lists (-> next meeting) ✔ * v4 list, core list, dev list * not much action on each of them, so maybe think about merging them to have one list for the topic "core/extension development" **TYPO3 4.7 Release Team Meeting - January 9th 2012** New: File Abstraction Layer (FAL) * A lot of work happened * Media Management won't be part of the core => filter bar of Vidi won't be available out-of-the-box * Included: file list (based on Vidy) Versatile Listing Engine (Vidi) ExtJS 4 migration * Revert everything that's related to ExtJS 4, require it only for Vidy-related extensions * => Solves current problems and does not break compatibility with 3rd-party extensions providing BE modules based on ExtJS 3 * Decision needs to be done, no time to make a public discussion first Pros and Cons of keeping ExtJS 3: * pro * works * skinning is fine * backward compatibility for existing 3rd-party extensions * cons * FAL filelist, 3 options * 1.) ship extjs4 for vidi * 2.) rewrite vidi for exjs3 (very risky) * 3.) rewrite on different basis * prolonging migration (=> put that in 4.8) * * reverting of the ExtJS 4 patches * loosing work Which options do we have? * 1.) go back to v3, and develop v4 to separate branch again * 2.) use ExtJS 4 for overall stuff finish everything, but extend release time of 4.7 (keep question to the public simple) ------- Old: **Agenda** * automating compile jobs within core (Steffen) * question on status of FAL (Olly) * question on status of ExtJS migration (Olly) **Automating compile jobs within core** * sprites are use at multiple parts in the core, however each time an icon is used a duplicate of that should be created * ExtJS 4 uses Sass and stylesheets need to be regerated * Steffen and Olly are going to talk about that after the meeting **Status of FAL** * Steffen and Benni have been meeting in Stuttgart for two days end of 2011 * Issues within project-fileabstraction that can be merged into Core separately BEFORE the merge of FAL * Signal Slot * TCEforms TemplaVoila Bugfix * ExtJS 4 Rendering Problems (Fonts) * Vidi? * Issues within project-fileabstraction that can be merged into Core separately AFTER the merge of FAL * tt\_content uploads * Migration Paths / Upgrade Wizards * Publishing Conecpt stuff? * External parts that will stay out of the core * * FAL Amazon S3 driver * FAL WebDAV driver * Media **Status of ExtJS migration** * skinning issues seem to be tackled * Steffen had a discussion with Kay Strobach to have native ExtJS modules integrated * Steffen will dump the results to have it available for all developers * Olly will contact Ernesto about spending money on that part (possible developers would be Stan Rolland and/or Peter Foerger) **General** * alpha3 gets postponed by one week to Januar 17th 2012 ------------------------------------------------ **Triggers to compilejobs...** * Sprites * on changes in directory: t3skin/images/icons/ * on changes in directory: t3skin/images/flags/ * * ExtJS Skin: * change in \url{http://git.typo3.org/TYPO3v4/Core.git?a=tree;f=typo3/sysext/t3skin/extjs;hb=refs/heads/master}