[TYPO3-core] SVN closed for now, do not commit!

[Franz Holzinger]

Hello

> Francois Suter schrieb:
>> - major release on demand: a major release could be decided when a
>> major project (like the new installer; I'm not being obsessive :-)
>> reaches completion. When the project is near completion a release
>> process would be started. Whatever feature is ready by then gets in too.
>>
>> - differentiated feature levels: one drawback of the current policy
>> (if I'm not mistaken) is that there are only minor release in between
>> major ones, and minor release are striclty bugfix releases. This means
>> new features can only get into major release. But there's a big
>> difference between a major undertaking like the cleaner backend and
>> the introduction of a new hook or transforming some TS property from a
>> string to a stdWrap, for example. Either such features should be
>> allowed into minor releases or maybe we should have an intermediary
>> level of releases (NMBNME = Not Major But Not Minor Either ;-). One
>> could imagine having 4.2, then bugfix 4.2.1 and 4.2.2, then 4.2.10
>> which would mark it as a minor release but with some new stuff in it.

I think this is a very good proposal.
And IMHO it would be better to have 4 numbers in the version for the future.
<main number>.<major changes>.<minor changes>.<only bugfixes>

This scheme would even help a lot with versioning of extensions.

Regards,

Franz