Daniel Gohlke extcode

## typo3_extension_versioning_concept.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                extcode
                / typo3_extension_versioning_concept.md
            
            
              Last active
              August 8, 2018 15:15
            
              
                TYPO3 versioning concept for extensions
              
          
    I've been thinking about a versioning concept for TYPO3 extensions for a long time. How can I handle different TYPO3 versions about throughout their live cycle? How should I handle deprecated TYPO3 APIs in newer versions? How can I handle new features, which maybe break some functionality in different TYPO3 LTS versions.
The main idea

Each TYPO3 version has an own branch. The branch of an extension for the most recent version of TYPO3 is the master branch or a branch which is in sync with the master branch.
If the extension supports a new version of TYPO3 a branch of the current master will be created for further development of non breaking features, tasks and bugfixes.
In the master branch the next commit will remove the support of older versions and replace all deprecated methods to the new ones.
v7.0.0 * | | 040cc7c [FEATURE] add support for TYPO3 v10 and remove support for TYPO3 v9

  
## FrontendUserHook.php
<?php

namespace Excode\CartExt\Hooks;

class FrontendUserHook
{
    /**
     * @param array &$parameters
     */
    public function showCartActionAfterCartWasLoaded(&$parameters, $refObj)
	<?php

	namespace Excode\CartExt\Hooks;

	class FrontendUserHook
	{
	/**
	* @param array &$parameters
	*/
	public function showCartActionAfterCartWasLoaded(&$parameters, $refObj)