kdevelop_3_3_branch

Mickael Marchand marchand at kde.org
Tue Mar 1 19:12:04 UTC 2005


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

Jens Dagerbo a ?crit :
| On Tuesday 01 March 2005 17:46, Matt Rogers wrote:
|
|>On Tuesday 22 February 2005 05:38 pm, Alexander Dymo wrote:
|>
|>>Hi!
|>>I've created a branch for KDevelop 3.3 development. Features, fixes, etc.
|>>are welcome ;)
|>
|>Discussion about the creation of this branch should have ensued before it
|>was created, because now I see problems with it:
|>
|>1. People will not know to checkout kdevelop_3_3_branch, HEAD stagnates,
|>people think we've stopped development
|>2. There is no timeline for qt 4 / kde 4 / kdevelop4 to begin
|>3. When it comes time to release, you'll have out of date translations.
|>
|>I think the kdevelop_3_3_branch should be merged back to HEAD and if
|>anything we use a branch for kdevelop 4 development.
|
|
| I must agree with Matt here. I don't understand why we branch for the
| continued development, and do porting in HEAD. Does this make sense in
some
| way that I don't understand?
|
| Merging back kdevelop_3_3_branch into HEAD and opening a porting
branch when
| any porting work is actually about to start seems much saner to me.
+1 :)

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

iD8DBQFCJLAyyOYzc4nQ8j0RAi11AJ9RL92vaYaZ2QZukyy6IOwPv9yVjQCgi9r6
/lzLtaMLfwnzlKsMYAM5yo8=
=bclF
-----END PGP SIGNATURE-----




More information about the KDevelop-devel mailing list