[TYPO3-commerce] Release new commerce version?!

[Michael Knabe]

Full ACK, using trunk as production stops us from working on major
issues that would break current installations. We could finally throw
away the support for older TYPO3-versions (like ext_autoload instead of
require_once, makeInstance with constructor arguments etc. pp.).
Maybe we can also get the "new" (by now 2 years old) payment system into
trunk then.

Cheers,
Michael

Am 18.04.2011 19:22, schrieb Christian Kuhn:
> Hey there,
> 
> we should release a new commerce version to TER, imho this is long overdue:
> - Current TER version doesn't really work with younger TYPO3 core
> versions anymore
> - There are tons of already fixed issues in current TER version
> - Nobody uses TER version anymore, everbody is nailed to trunk as
> production version
> - There is afaik currently no major blocker, and if, we can still
> release new branch versions
> - Current 'trunk is production' stops us from badly needed refactorings
> of given codebase
> - There are new labels in trunk which does not make sense to be
> translated on translation server until we have a new TER version online.
> 
> What I think would be best:
> - Release current trunk 'as is' as new TER version
> - Create a branch to be able to merge bugfixes from trunk to this branch
> to release minor TER updates if needed
> - Raise TYPO3 dependency to TYPO3 4.5 in ext_emconf in trunk and start
> with clean ups in trunk (thinks like 4.5 compatibility (eg. new tree),
> remove deprecated methods, don't use old deprecated methods from core,
> maybe switch to fluid as template engine, ...)
> 
> Any opinions?
> 
> Regards
> Christian