Spotkanie zespołu release s - CMS TYPO3 6.2 LTS
##Probe
Musi być omówione, jak sobie z tym poradzić.
\url{https://review.typo3.org/27024}
##Następne Spotkanie 2013-12-31?
Godzina: 14:00 CET
Jeśli ta data i czas nie pasuje ze względu na X-mas uczuć itp.,
proszę podać informacje zwrotne Ernesto i / lub Olly.
Tematy:
* Powiadomienia poczty Travis nie wysłany - definiowanie adresów, które zawsze są zgłoszone na awarie
*
##Meeting 2013-12-16
Time: 14:00 CET - 15:20 CET
Participants: Ernesto Baschny, Michael Stucki, Oliver Hader, Matthias Schreiber (as guest)
h2. General "hot" topics
* \url{https://notes.typo3.org/p/CGL-decisions}
** @todo Benni
* \url{https://notes.typo3.org/p/Realtime-Communication-Channels}
** easy the pain to switch to IRC
** put Ries' IRC logs to typo3.org infrastructure - \url{http://forge.typo3.org/issues/54022}
** proxy services - @todo Olly asks Chrstian Müller about his experiments in that regard
** create policies for IRC channel to keep traffic low - @todo Olly checks whether Neos team has something already
h2. Status of TYPO3 CMS 6.2 LTS work-packages
In general, @todo Ernesto is going to write an article about these work-packages and the current status of TYPO3 CMS 6.2.
* File Abstraction Layer
** Steffen started working already on several FAL issues
** besides that a possible blocker in the generic driver API has been discovered that needs proper development and reviews
* Extbase: Felix needs some input if he can / should do something, as he is unemployed. I gave some ideas and asked him to talk to MaBa. Ernesto could coordinate, but has very little insights in Extbase to really be able to evaluate the work. Anja is available and also mentioned that Alex Schnitzler has indicated willingness to help if required.
** Performance (BE Bootstrapping)
*** Optimize TypoScript loading and parsing by e.g. caching or alternative notation of configuratiuon (instead of TypoScript text, e.g. arrays or YAML)
*** Optimize disposal of ArrayUtility in Extbase
** Workspaces / Languages support (as already conceived). Felix estimates 6 pd of work (incl the tests cases)
* Importer/Exporter: I would rather prefer MaBa to "finish the work" he started instead of giving that to yet another person (thai). They can be involved in reviewing thou.
** \url{https://review.typo3.org/#/c/25294/} - "**File handling in import/export module is broken"** (general patch, does not fix the real import problems)
** \url{https://review.typo3.org/#/c/22939/} - "**Fix impexp for importing exports from version 4.x"** (backward compatibility to 4.5 and fixing import problems) #ThaiForward
** Mattes will give this to Dieter tomorrow (Dec. 17th. 2013)
* Workspaces with Relations (IRRE/MM):
** Tymek might start to work on the functional test cases - I required, Olly can provide a kick-start for tests and testing framework
** @todo Olly asks Sascha Egerer and Thorsten Kahler concerning availability
h2. Issues to be discussed
h3. Backporting Strategy in general
* Ernesto: Maybe we should add "minor version regressions" to the group of "important fixes" that we might *consider* for a backport. I.e. some refactoring removed a functionality (by mistake) and it needs to be re-added to some newer version. This is something that could be backported as a re-addition to all previous versions.
** consider "broken-features" (behaviour that once was working, but bug has been discovered later) as target to be back-ported
** actively maintain TYPO3 CMS 6.1, since it's the most recent stable branch - thus, continue regular support until TYPO3 CMS 6.2 LTS is released
* Feeling: The CMS team has to decide together (i.e. by voting) on backports, because it involves a chain of releases and it cannot be up to the RM of each release if something gets included or not (else it lacks consistency - is included in 4.5 and not in 4.7).
** Mattes: +1
* Visualization of maintenance phases
** see \url{http://forum.typo3.org/index.php?t=msg\&th=200732\&goto=700981\&#msg\_700981}
h3. Current issues:
List of issues that are pending to be backported to TYPO3 4.5 and/or 4.7, which are in "only security / priority bugfixes" status.
It's up to the Release Team to find a final decision whether to approche or decline changes in question.
We should rather not discuss these individually, but decide offline and only discuss controversial ones:
* **[BUGFIX] Get suggest wizard working with renderMode=checkbox**
** \url{https://review.typo3.org/#/c/18689}
** pre-votes
*** Steffen Ritter: -1
*** Helmut Hummel: -1
*** Mattes: Does it work? No. Did it work? No. -> No backport
*** Ernesto: -1 for older branches, +1 for 6.2
=> -1 for backports, +1 for master
* **[BUGFIX] TS is fetched from cache incorrectly sometimes**
** \url{https://review.typo3.org/#/c/18062/} (old)
** \url{https://review.typo3.org/#/c/24981/} (4.5)
** \url{https://review.typo3.org/#/c/24182/} (4.7 already merged! - already merged in 6.0-6.2 too)
** branches: all
** pre-votes
*** Michael Stucki: +1 :-)
*** Helmut Hummel: +1
*** Ernesto +1 for 4.5 too to be consistent, but there are not tests yet
=> +1 for missing 4.5 backport
* **[BUGFIX] Use init.php for initializing constants in thumbs.php**
** \url{https://review.typo3.org/#/c/20731/}
** branches: 4.7 (only?)
** pre-votes
*** Steffen Ritter: -1 FEATURE aka change of behaviour
*** Michael Stucki: +1 @steffen: I wouldn't propose this if it our sites wouldn't break without it. In fact, it fixes a serious bug, but I don't know why it doesn't happen at many places. Read the description...
*** Helmut Hummel: -2 for 4.5, -1 for 4.7 This is very unlikely to happen that a thumbs.php is called standalone and not within a request that already writes the cache. This is a typical case for a verly low priority bugfix and the decision we have taken to not include these.
=> controversial?
=> discussed with Michael and we agreed on not back-porting
* **[BUGFIX] use search word(s) for ordering search results (again)**
** \url{https://review.typo3.org/#/c/20294/}
** pre-votes
** branches: 4.7
*** Oliver Hader: +1 since it was broken in 4.7.0, but worked in older branches
*** Mattes: does it work? No. Did it work? Yes. -> Backport
*** Helmut Hummel: +1
=> +1 for backport
h2. New version of the share font
Ralph du Carrois is going to release a new version of the share font which is used for the TYPO3 project in general.
Ralph plans to have a commercial version of the font, but grants free usage of the font for the TYPO3 project (exception to the commercial license).
h2. Redmine Update
Server team plans to update Forge/Redmine until mid of January 2014 (at the latest).
##Meeting 2013-11-11
h2. No release team meetings during the last few weeks
h2. T3CRR13 sessions
* community activity
** \url{http://metrics.andygrunwald.com/statistics/gerrit/activity-monitor/analysis/61/}
* migration project
** \url{http://www.typo3camp-rheinruhr.de/sessions/2013/session/show/62-migaration-von-4x.html}
h2. File Abstraction Layer issues
* \url{https://review.typo3.org/#/c/24747/}
* \url{https://review.typo3.org/#/c/23398/}
h2. Responsive Introduction Package
Benni will continue to work on the new Introduction Package. Besides that, marketing-factory offered help in finishing the package, especially since their developers had been working on the responsive images feature in TYPO3 CMS 6.2.
h2. Further issues
* problems with import/export process lead to inconsistencies (possibly the reference index is invalid)
* performance issues with recent version from Git master, see \url{http://forge.typo3.org/issues/52949}
** possibly race conditions after caches have been cleared
** improvements for the pages cache, see \url{http://forge.typo3.org/issues/53404}
** PackageManagement class loader possibly checks files to be loaded twice
h2. Further topics
* documentation concerning upgrading TYPO3 4.5 LTS to 6.2 LTS
** \url{http://docs.typo3.org/typo3cms/InstallationGuide/Upgrade/Index.html}
* user interface changes
h2. Marketing and Strategy sprint in Altleiningen
##Meeting 2013-
Topics:
* Budget Request, ok, @todo Olly will give feedback. Maybe add "LTS maintainance"
* Leader voting: Olly talked to Ben
* Alpha3
* Distributions
*
* FAL
*
##Meeting 2013-09-20
Agenda
* CMS Code Sprint \url{http://doodle.com/bmw965yx5iedv7r3}
* Alpha3 next Tuesday
* FAL WIP from Steffen \url{https://github.com/nxpthx/TYPO3.CMS/tree/fal62}
* First review \url{https://review.typo3.org/23839}
Olly Workspace stuff: next week
##
##Meeting 2013-09-03
###Agenda
* 6.0+6.1 releases and how to proceed
* 6.2 Status (FAL, Packaging, others?)
* Blueprint Concept
* Sprint October
###h2. 6.0+6.1 Releases:
Regressions
* #51747 when deleting typo3temp/\_processed\_
=> maybe other regressions mentioned in this issue
* #51733 in migration upgrade wizard
* \url{http://forge.typo3.org/issues/51761}
* \url{http://forge.typo3.org/issues/51767}
* Helmut asks how we can get more people to test sec-releases before hand
* an idea would be pre-releases for "interested agencies"
###h2. 6.2 Status
h3. Packaging (Responsive / Introduction ...) Status
* Does Benni have time to work on that? @TODO Benni will update us on the status tomorrow
* Should Susanne do more? We need to test this... \url{https://review.typo3.org/#/q/project:Packages/TYPO3.CMS+branch:master+topic:distributionmanager,n,z}
* Idea: basic core EM should only display distributions from TER user "typo3v4"
* @TODO: create a new TER user "typo3cms" and transfer some from the typo3v4. See also \url{http://forge.typo3.org/issues/51620}
* @TODO: olly should get the info on the new typo3cms user
* Prios: Finish introduction package. Then government and then a translated gov-pack
h3. FAL status:
* @TODO: Plan a Skype meeting in the next days with the relevant guys. We need Olly!
* Localization: What and how can we achieve this major goal for 6.2 in the next weeks?
* Focus on API.
* TypoScript API! Helmut: Unify the ways to refer to files.
* @TODO Ernesto: check if Patrick could help with the TypoScripting API and css\_styled\_content
* Clean Core FAL API usage mess (ElementBrowser and others). Core code should be the "guideline" on how to use it!
* Steffen has some WIP patches he'll push
Currently Blockers
* FAL Translations
* IRRE Workspaces
After Feature Freeze
* Performance
* Restructuring
h3. Session Storage by Thorsten Kahler
* #51731 Store sessions outside DB
###h2. Supported software versions
We should think about the MySQL, PHP, Browser Support for our TYPO3 releases, especially rethink them in LTS versions as time passes.
4.5:
* PHP: as of now: 5.2.x - 5.3.x => we should support PHP 5.4/5.5 also
* MySQL: as of now: 5.0.x - 5.1.x => we should also support MySQL up to 5.5
* Browsers: >IE6 and all other shit => still ok
4.7:
* PHP 5.3.x => we should support PHP 5.4/5.5 also
* MySQL: 5.0.x - 5.1.x => OK
* Browsers: IE7+ and others?
6.0:
* PHP 5.3.7 - 5.4.x => should also include 5.5
* MySQL: 5.1.x - 5.5.x => OK
* Browsers: IE8+ and others? (no more IE7, is that ok?)
6.1:
* PHP 5.3.7 - 5.4.x => should also include 5.5
* MySQL: 5.1.x - 5.5.x => OK
* Browsers: IE8+ and others?
6.2:
* PHP 5.3.7 - 5.4.x => should also include 5.5
* MySQL "and compatible": 5.1.x - 5.5.x => include 5.6 (released 2011-04) (with some compat-mode set @TODO Benni will check which config was required). Not yet 5.7 (released 2013-04)
* Browsers: IE8 and the fancy shit? => We might need some IE8 "task force" or invite customers to test this more throughoutly (especially new features)
* @TODO ask the community if IE9 would be ok
* @TODO Ernesto: article about
###h2. Blueprint Concept
* \url{http://wiki.typo3.org/Blueprints}
* Make it official?
* try to "use it more"?
###h2. Code Sprint in October (Stuttgart?)
* Dates set, location unclear, probably Stuttgart
* \url{http://doodle.com/bmw965yx5iedv7r3}
###h2. Communication via IRC in the future? (Benni)
* Helmut totally agrees!
* We only have to solve the log history part by providing a bouncer service
* @TODO Benni will check with Christian Müller how they work with it (Neos/Flow)
* Flow/Neos Web Logs through Bots: \url{http://riesvantwisk.com/cms/home/irc-logs.html}
* See also \url{http://www.dozeo.com/} (idea from Benni)
###
##Meeting 2013-08-02 - open for Active Contributors
Ernesto:
* Michael Schams wants to create a "editors migration guide / doc". Ernesto welcomes the idea and invited him to open an issue in the Smooth Migration project
* He also will create the "official what's new slides" - probably in collaboration with Patrick Lobacher and Roberto Torresani (Italy)
##Meeting 2013-07-26
Patchlevel Release
* Tests in Travis needs to be green before a release
* Christian stressed the need to keep travis green all the time (prioritize fixing it if it gets red!)
Agency Sprint
* Already 6-7 inquiries
Regressions so far (only 6.0..6.1):
* \url{https://forge.typo3.org/issues/50417} Extbase
* \url{https://forge.typo3.org/issues/50363} FAL
Documentation Backend Module (Xavier)
* \url{https://github.com/fsuter/TYPO3.CMS.Documentation.Migration/}
* Requirements: CSS/JS cleanup (mostly)
Meeting with Active Contributors
* Skype Meeting with whole team instead of RTM next week: 1st August - 15h CEST
AfK = Away From Keyboard
TER Cleanup Project
* patch for TER / typo3.org is ready, needs to be merged: to check typo3 dependencies on upload of a new extension
* next step: mark OUTDATED extensions in TER
* typo3.org sprint end of august, might be solved there
* Steffen Ritter will try to get in touch with the typo3.org/TER guys
* Xavier will open up an issue in the typo3.org tracker
FAL Code Sprint Mainz August 5-8 2013
* Steffen Ritter will be joining 2-3 days
* Olly will try to be there 2-3 days
##Meeting 2013-07-18
Olly doing Workspaces:
* general UI and performance improvements
* besides that concept phase for overlay strategies (MM, IRRE, Extbase, ...)
Reimbursements:
* T3ACME13N, currently ca €2.600 spend for that meeting
* T3DD Budget €550 per person. Ernesto will inform team via Core List
FAL / Media Code Sprint:
* to be planned
Introduction packages:
* *.txt files: \url{http://forge.typo3.org/issues/49418}
* Extension status: \url{http://forge.typo3.org/issues/45029}
* Status of Benni's work on "Responsive Package"?
* Olly asks Benni
Design / UX:
* Jens is searching for a tool for designers / UX guys to review screens. See \url{http://forge.typo3.org/issues/49149}
* Several topics have been categorized by Jens last year (some are solved already): \url{http://forge.typo3.org/projects/usability/wiki/T36\_UIXU\_sprint\_ffm}
Migration Code Sprint Status
* its going ;)
TYPO3 Stable Releases
* Stable Releases next tuesday (23th July)
Meeting about FLUID yesterday
##Meeting 2013-07-11
Release Agenda Image and 4.7 extended Support: where to find it?
=> put it here? \url{http://typo3.org/roadmap/}
##**Meeting: 2013-06-13, 2pm CEST**
*
From last weeks meeting:
* CLA issue: ~olly: will notify licensing team and if there aren't any objections, message to core list => DONE?
* will contact Olivier
* Target Versions cleanup: Ernesto still has to announce that properly
* will write to list
TYPO3camp Stuttgart, reactions to talk:
* questions about "deprecation strategy"
* will the plan hurt TYPO3 Neos effords (by keeping developers on CMS)?
* when will Flow be integrated in CMS?
* missing communication "why this will be done"?
* was filmed by someone I know, he promised to send me the video
TemplaVoila discontinued - or not...
* should we announce / write something from the TYPO3 CMS Core Team perspective? i.e. at "buzz"?
* "team" building to continue maintain it at least for 6.2 LTS release
* Wouter's tries \url{https://github.com/wouter90/templavoila/}
* Tolleiv aware and will call in a "Group meeting" with interested persons
* ~olly will talk to Joey about comparision to gridelements / be\_layouts
* ~olly: Article in Buzz
Workspace Code Sprint
* Results? discussions and reviewing patches at dkd.
* WIP? Joey and Thorsten will document the decisions and changes to be made. Tests with Siesta. Functional testings.
* Information for upgraders required: \url{http://forge.typo3.org/issues/49076}
* Notes from the sprint: \url{https://notes.typo3.org/p/wsvcs13ffm}
Language handling (content fallback problem)
* Markus Klein, Stefan Galinksi: \url{https://review.typo3.org/9937}
* Stefan Neufeind: \url{https://review.typo3.org/14464}
* Report with analysis by Rainer Becker: \url{http://forge.typo3.org/issues/48673}
* ~olly will check it out
UX Meeting tomorrow in FFM
* \url{http://doodle.com/b8skviip5cfk395m}
* Jens, Lars, Benni, Ernesto, Felix, Robert, Martin (Engel)
Install Tool
* Status: core functionality works
* refactoring phase, "step handling", "tool handling"
* UX should be redesigned afterwards
* Check it out at Catharsis
Smooth Migration project
* Announce today: \url{http://forge.typo3.org/projects/typo3cms-smoothmigration/wiki/Draft\_Initial-Announcement}
* Write article for extensions: \url{http://forge.typo3.org/issues/49094}
* Ernesto talked to Jochen at the T3CS who promised a list of "top used extensions" \url{http://forge.typo3.org/issues/48573}
PhpUnit Code Sprint
* \url{http://wiki.typo3.org/PHPUnit\_Code\_Sprint\_2013}
* Steffen suggested to have a Category:CodeSprint to be able to filter all wiki entries that describe a code sprint
* Issue created: \url{http://forge.typo3.org/issues/49103}
* **Last Meeting: 2013-06-03, 2pm CEST**
Topics
6.2 Related:
* Logging Roadmap published by Steffen Müller \url{http://forge.typo3.org/news/646}
* Discuss "Split-up module menu (integration \& system)" \url{https://review.typo3.org/#/c/21177/}
* and other similar backend UI changes "in the planning". Discuss the scope of "backend changes" for TYPO3 6.2 LTS.
* Upgrade Project
* \url{http://forge.typo3.org/projects/typo3cms-smoothmigration}
* Mittwald will make an "interview" with Ernesto for their Blog (as usual), he's waiting for the questions
* 6.2.0alpha1 today
* automaketemplate patched
* tt\_news patched
TYPO3 CMS Mission / Vision Related:
* An user mentioned to Ben that "nobody knows where to get information on TYPO3 6.x". Ernesto asked back some more details on what is expected etc, no feedback yet
* "Vision Document" is still unfinished and would be a good asset (sorry for that ~hh)
* Steffen Ritter did a talk about the "Vision" in T3CON-NA, maybe he could share the slides or tell us about the reaction
* \url{http://de.slideshare.net/sritterkh}
General and Infrastructure:
* Gerrit Update:
* can change commit messages "inline"
* avatars!!!
* CLA or not CLA for contributing to TYPO3.CMS.Flow and Fluid - need an official statement (reminder by Anja)
* no forward ports from extbase to flow : no CLA required
* potential forward ports from Fluid only need CLA at forward porting time
* ~olly: will notify licensing team and if there aren't any objections, message to core list
* Forge "Target Version" Cleanup
* Deleted all Target Versions with no issue assigned
* Need to reassign all issues Target Versions to delete them: easy solution: keep them?
* Ernesto already cleaned up actual target versions, only left are:
* next-patchlevel
* 6.2 LTS
* 6.3
* Policy now should be "only RM / Team Leaders" set Target Versions
* Extbase / Fluid team seem to be fine with their Target Versions (Extbase 6.2, Extbase 6.3, Extbase 4.5 etc) according to Anja
* Projects on Forge:
* **Advanced FE-Editing** still Subproject of Core: **Move to "Extensions"? **\url{http://forge.typo3.org/projects/typo3v4-feedit}
* **DBAL Issues**: Move to Core and close Subproject? \url{http://forge.typo3.org/projects/extension-dbal/issues}
* **Indexed Search**: Close Subproject? \url{http://forge.typo3.org/projects/typo3v4-search}
* **jQuery Integration**: Subproject of 6.1 still. Move to 6.2? Issues still relevant? \url{http://forge.typo3.org/projects/typo3v6-jquery}
* Ask Benni about how to proceed
* We could close the project, but still need proper Documentation, i.e. continue with \url{https://notes.typo3.org/p/jquery-guidelines}