[Typo3-dev] TYPO3 version 4.0.0?

[Robert Lemke]

Well guys, I thought you were sleeping at night? We should make up some
rules that no important discussion may be led between 12pm and 6am ...
;-)

I don't have to add anything interesting to the version number debate
except that I don't like big jumps without something big happened. And
in my opinion the "cleanup sessions" are something big as well (see
kernel 2.6)

On Wed, 2004-04-21 at 02:19, Kasper Skårhøj wrote:
> This leads to another question: Since the core will soon be enhanced
> only with boring APIs/hooks/bug-fixes maybe we should introduce
> "official extensions".
> 
> "Official extensions" are the cream of the crop. They are under quality
> control, they have dedicated development team, they have goals etc. The
> "Official extensions" will be presented inter-mixed with the TYPO3 core
> features and as such as a whole to the world around us. 
> 
> As I see it the only way you can get marketing punch from a new TYPO3
> core version is to market it along with a synchroneous release of the
> "Official extensions".

Yes, I definately like the idea of "official extensions" or whatever you
call them. 

More than that I would like to form a main distribution package
containing these important extensions which have proved to be stable.
And while we're at it we could have packages like these:

- typo3-3.6.0-distpkg-stable.tgz

  Contains a stable 3.6.0 with only stable "official" extensions. The
  state of the extensions and the core is frozen except for

- typo3-3.6.0-secpatch-29.t3p

  security patches. These patches are only available for the stable
  branch and may be installed by a patch extension. A modified extension
  manager might warn TYPO3 administrators if new security patches
  are available.

  Patches should be available for the frozen core as well as for the
  frozen official extensions.

  After typo3-3.6.0-distpkg-stable was frozen, development for the   
  official extension continues of course. As long as they still work 
  together with 3.6.0, hopefully stable interim releases will be 
  published in

- typo3-3.6.0-distpkg-testing.tgz

  which contains the stable frozen 3.6.0 core (with security 
  patches applied) including the updated official extensions. 
  I could imagine that this package gets build automatically 
  (or semi-automatically) from the official extenion's
  CVS for versions which have a certain tag.

  The further development of the core will be available through CVS. If 
  it reaches a beta / RC state, only the core would be published as a 
  dummy package (maybe we could also rename that to core package):

- typo3-3.6.1b4-corepkg.tgz

  I don't know if it makes sense to also have dist packages (ie. 
  including official extensions) for beta and RC releases. The target
  group of these releases should be people who know what they are doing,
  so only releasing core packages might be okay for them.

Besides from that there could be other packages for certain purposes
(like distributions of different flavours).

What do you think?

-- 
robert

"They placed me on this earth without a manual. 
 And I dare to say, I’m doing just fine without ;)"