[TYPO3-core] Fixing no-brainers?

[Ingmar Schlecht]

Hi Martin,

thanks for the good input!

Martin Kutschker wrote:
> Do we fix stuff like bug #2938 in TYPO3 4.0.1 or has this again wait for 4.1?

Yes, I think such things can go to both 4.0.x and HEAD.

> Which brings me to the topic of the next release. This is what I had in mind for it:
> 
> Let's start with fixing a couple of urgent stuff in 4.0.1 and possibly 4.0.2.
> Better have a 4.0.1 in one week and 4.0.2 after that in three weeks than only
> one 4.0.1 in two months.

Yes, I totally agree. After all, some people still haven't upgraded to
4.0 and they will be happy that they already get the 4.0.1 with some
bugs fixed when they start upgrading.

@Michael Scharkow: I think too many patch level releases is never a
problem, because people can just stay with 4.0.0 if they like to.

> Then target an intermediate 4.1 that will mainly clean up and streamline 
> stuff of the new features. I think that a widespread use of eg workspaces 
> will bring up some issues that need polishing. This release should not 
> very far from now. Perhaps 3 to 6 months from now.

Exactly!

> Parallel to 4.1 we could work on the BE UI overhaul that's the goal for 4.5. 
> I think we should in this case don't work on HEAD, but in either a branch 
> or on local systems so the tree doesn't get destabilized. Since these 
> changes will be major and will take more time I suggest work on this 
> will be started before the release of 4.1 (hence the new development[!]
> branch that is to be merged into HEAD).

Good idea!

So then we would have those branches:
 - 3.8 (only security fixes)
 - 4.0 (security fixes, urgent bugs and no-brainers)
 - HEAD (4.1) (bigger fixes/changes to things like Workspace)
 - 4.5 (UI and radical architectural changes)

I'd propose to change this slightly, to:
 - 3.8 (same as above)
 - 4.0 (same as above)
 - 4.5 (what's called HEAD (4.1) above)
 - HEAD (5.0) (what's called 4.5 above)

That is developing the most radical changes in HEAD and calling the
result 5.0.

The initial road map by the R&D team has planned the UI changes for 4.5
and the radical architectural changes for 5.0 but I think they have to
be combined.

> PS: I'm not happy that older vesions of TYPO3 are not supported. 
> Michael Stucki's remark that there is no need for a 3.8.2 made
> me think if not somebody wants to take over the burden of maintaining 
> the old stuff. This is happening with Linux and Apache, so why not 
> with TYPO3? 

I agree with you that having better maintenance of Branches would be
good and think we should start it beginning with 4.0.
But IMHO it's impossible to merge the 4.0 bugfixes back into 3.8.

cheers,
Ingmar