[TYPO3-ttnews] Time for tt_news 3.0 ?

[Rupert Germann]

hi Ingo

since TYPO3 was renamed to TYPO4 last week I thought the 3 was free for
other purposes ;-)

seriously:

from a coder's point of view I understand your points - but the coders among
the tt_news users are only a small minority.

The majority of users are the day-to-day tt_news editors and admins which
only see the GUI and the config options and not the code.
If I look back on the previous tt_news versions, there had never been so
many GUI related changes in one release at once since introducing
flexforms. 
And exactly those day-to-day tt_news users will be stressed to look a bit
closer to the docs before updating their production sites with the new
version if there's a new main number in front of it.

There are enough numbers left to make other releases, but for now we will
stay with the 3.

greets
rupert
  


Ingo Renner wrote:
> I largely disagree at this point! 2.6 is the right number! 3.0 should be
> an even more fundamental rewrite of tt_news. Sure we all love tt_news.
> But on the other hand it has so many shortcomings when it comes to
> usability, configuration, maintainability, and extension.
> 
> Nobody can blame Rupi or anybody else who put work into tt_news for
> these things - heck I would even blame myself as co-developer of tt_news!
> However from that position of the co-developer and the experience I
> gained during studies, my role as Release Manager for TYPO3 4.2, and the
> work with TYPO3 in general and tt_news as a single project I also can
> say that many new and improved ways of development turned up since I
> started to work with TYPO3.
> 
> In my eyes a 3.0 version of tt_news is only worth it if a rewrite is
> done from the base up in a far more object oriented way than it is
> today. This will make it easier to understand, extend, and especially
> work with tt_news.
> 
> So again, 2.6 is the correct increase of the version number; Don't go
> for 3.0 just for the sake of it. A full version bump would allow us to
> break everything, while we would give away this chance now. Of course
> XCLASSes will break with 2.6 but IMO this is always tolerable - even
> with 2.5.x+1 releases.
> 
> yours
> Ingo
>