[TYPO3-commerce] Release new commerce version?!

[Torben Hansen - Skyfillers]

Hi,

I think this is a great idea. 

It would be great, if the new development version could include some of the reported bugfixes (which include patches) from forge. We discovered some performance issues which we have fixed and submitted to forge. There are also several other useful patches, which "just" has to be reviewed/approved/implemented into the new trunk.

How many of the team members do still work actively on the project? When the new development version is ready, I could help fixing some bugs from Forge.

Best regards
Torben

> -----Ursprüngliche Nachricht-----
> Von: typo3-project-commerce-bounces at lists.typo3.org [mailto:typo3-project-
> commerce-bounces at lists.typo3.org] Im Auftrag von Ingo Schmitt
> Gesendet: Dienstag, 19. April 2011 12:23
> An: TYPO3 commerce extension project
> Betreff: Re: [TYPO3-commerce] Release new commerce version?!
> 
> Hi,
> 
> I can do this during the easter holidays. I would relase the current version
> (0.12.x) to TER, since 1.0 would be stable release.
> We could start the new 4.5 development by version 0.13.. BTW how could take
> care of the open Todos in forge?
> 
> Regards
> 
> Ingo
> 
> > Hi Christian,
> >
> > i think is is an good idea.
> >
> > We should release the current trunk as 1.x branch and the trunk would then
> be 2.x.
> >
> > Greetings,
> > Benny
> >
> > "Christian Kuhn" <lolli at schwarzbu.ch> schrieb im Newsbeitrag
> news:mailman.17201.1303147387.648.typo3-project-
> commerce at lists.typo3.org...
> >> 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
> >
> > _______________________________________________
> > TYPO3-project-commerce mailing list
> > TYPO3-project-commerce at lists.typo3.org
> > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-commerce
> >
> >
> 
> 
> Mit freundlichen Gruessen
> Ingo Schmitt
> 
> *** BITTE BEACHTEN SIE UNSERE NEUE ANSCHRIFT! ***
> 
> --
> Marketing Factory Consulting GmbH  *   mailto:is at marketing-factory.de
> Marienstrasse 14                   *          Tel.: +49 211-361176-63
> D-40212 Duesseldorf, Germany       *          Fax:  +49 211-361176-99
> Amtsgericht Duesseldorf HRB 53971  * http://www.marketing-factory.de/
> 
> Geschaeftsfuehrer:    Peter Faisst   |   Katja Faisst
> Karoline Steinfatt   |   Christoph Allefeld   |   Markus M. Kimmel
> 
> _______________________________________________
> TYPO3-project-commerce mailing list
> TYPO3-project-commerce at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-commerce