Re: [REQ] commiting bugfixes to stable 1.4 branch

Hi Stipe,

On Fri, 2004-12-03 at 01:27 +0100, Stipe Tolj wrote:
> for all developers with cvs access, please obey to commit bugfixes that are 
> logically fixing issues in the current 1.4.0 stable release to _both_ branches: 
> HEAD and stable_1_4_0
> 
> We will use the stable_1_4_0 branch to release an updated stable release called 
> 1.4.1 after some fixes have been applied.
> 
> Feature adds and things that are new should go into HEAD. Fully experimental 
> code should go into an own branch, as Alex did this for the new autoconf stuff.
> 
> Is this policy ok for all? I just want to prevent to mess up the HEAD branch, 
> when releasing 1.4.1 (stable) and have code inside that is "yet not fully 
> tested" or something similar.

This is the same policy naturally used by many other (larger?) free
software projects like KDE and GNOME I guess; although GNOME release
process has a bit more complex set of rules I believe.

Rock!
-- 
Enver ALTIN                   |        http://skyblue.gen.tr/
Software developer @ Parkyeri |      http://www.parkyeri.com/

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

iD8DBQBBr9MUZCB2FZvqK0sRAnrxAJ4rkE1gvBTfstJlyaf1uuDpKudDOgCfb7nO
3d2m7iL2mJw2LyEDP3Khnfc=
=86CL
-----END PGP SIGNATURE-----