[eGroupWare-core] new release model for the time after 1.2

[Lars K. <l.k...@me...>]

Hello!

Currently we have very, very long release cycles. I would like to
propose a new release model to get more release in a shorter time.

At the last Linuxtag we had already some discussions about it. The main
idea was to split up the big egroupware package in smaller packages.
That would allow us to release any egw app when it is stable.

But that's something that the distributions don't seem to like so much.
To much overload to get egroupware running.

But i have another idea, which should solve our problems! :-)

When the 1.2 release is out, we create a new stable branch. In the
beginning this branch is equal to the 1.2 branch. When ever some
developer thinks that his app currently in a stable state, he merges
this version to the stable branch.

That would allow the releasemanager team to build stable release on a
regular basis and would allow us to build stable release very fast.

Currently we only put patches in the 1.0 branch which keeps the new
features away from the users for a very long time.

What do you think?
-- 
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 4
20457 Hamburg
Germany

eGroupWare Hosting, Development, Support and Training

E-Mail: mailto:l.k...@me...
Web:    http://www.metaways.de
Tel:    +49 40 317031-21
Fax:    +49 40 317031-81
Mobile: +49 175 9304324