Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Blueprints/ReleasePackages

From TYPO3Wiki
Jump to: navigation, search

<- Back to blueprints overview

Blueprint: ReleasePackages

Proposal ReleasePackages
Owner/Starter Nicole Cordes
Participants/Members -
Status Draft, Discussion, Voting Phase, Accepted, Declined, Withdrawn
Current Progress Unknown, Started, Good Progress, Bad Progress, Stalled, Review Needed
Topic for Gerrit releasepackages

Target Versions/Milestones

  • Started during ACME in Munich 2014

Goals / Motivation

During the ACME 2014 in Munich a proposal to split the system extensions in different layers was presented. Felix Kopp proposed to divide the core functionalities into "core", "edit", "manage" and "present" layers.

This is really a good idea as we can use the TYPO3 CMS release packages in multiple ways:

  • Framework for module work
  • Backend use only
  • Backend and Frontend

Concept

Multiple steps have to be done:

  • divide current system extensions and move functionalities to own / other extensions
  1. minimal core version with installer, be_users management, backend to register / use modules, language handling
  2. manage version with backend record handling, sysfolders for management, own page tree
  3. complete version with backend and frontend
  • decentralize layout/skin configuration

Implementation Details

Risks

Issues and reviews

Dependencies upon other Blueprints

External links for clarification of technologies