[TYPO3-core] RFC: Hook request in t3lib_tceforms

[Thorsten Kahler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Bernhard,

Bernhard Kraft wrote on 14.02.2007 18:05:
>> However, I still think that a hook is not a feature, and therefore should be
>> ready for introduction as long as the final version *.0 is not ready.
> 
> I did not meant this patch for 4.1 ... i knew that we have feature 
> freeze as RC1 is out already.
> 
> Sorry I missed to add:
> 
> Branches: Trunk only
> 
> in the RFC
> 

as long as there's no TYPO3_4-1 branch we have feature freeze in trunk. You
might call it a dead lock situation because noone can change anything but
fix bugs.

The release manager(s) probably have forced this situation to put more
manpower into bug fixing than into new features ;-}

OT:
I consulted the "Core Team Guide 0.2" on the topic and the statement I found
was <cite>New branches and tags are usually created by the release manager
whenever it is needed, so you should not do this on your own. You can
contact the release manager if you have special requests.</cite>
Branches are mentioned at some other places in the document also, but there
the process isn't described in detail as well.

AFAIR the last discussion on the core list had the conclusion that a RC
means a new branch. I support this.

I think there's no discussion about following points:
- - A RC means a feature freeze.
- - A feature freeze does allow no changes but bug fixes.
- - No new features but only bug fixes can get into a branch.

What's the result of this?
If we have a RC _without_ a branch, it's not allowed to do any other changes
on trunk than in a branch. So there's no difference between the trunk and a
branch. And we have the absurd situation of the trunk being a branch.

Ergo:
RC => feature freeze => branch


So IMHO something like these lines should be added to the "Core Team Guide"
(if there are no objections):
A branch is usually created with the RC1 ( the first release candidate) of
a new minor version whereas tags are created for every release ( beta, RC,
final and patch level).
every patch level version.
The versioning scheme is "<major release>.<minor release>.<patch level>".
According to this the (regular) branches are named "TYPO3_<major
release>-<minor release>" whereas the (regular) tags are named "TYPO3_<major
release>-<minor release>-<patch level>".


/OT

Regards
Thorsten



- --

Thorsten Kahler

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFF03KBmfCxYiz3uLkRAsRVAJ9Acd0Pspnp+cWGZwU0DpQKQNQBsgCeKklL
CtcNbpx+CGHTCsIzhOuoou8=
=Tik9
-----END PGP SIGNATURE-----