release policy after KDevelop-2.1

[W. Tasin]

Hi!

I really don't like the idea maintaining 3 branches.

On the other hand the situation in our department in the University of 
the Appl. Sc. is the following:
- We already use KDevelop 2.0 and still use KDevelop 1.4 on KDE 1, but 
we will NOW update
   the the rest of our PCs to KDE 2  (half of them were already updated 
last summer) and so update to
   KDevelop 2.1
- For practical training lessons we need a stable version for KDE 2 for 
developping
   console applications in ANSI-C and ANSI-C++
- The requested features (by profs and students) are already committed 
and I hope that there will no
   bug report or feature req. on it
   [ let's say: "I have a dream...." ....
   I think unless the standard version of KDE in the distributions isn't 
KDE 3, we will support KDevelop
   for KDE 2 (or at least I have to support it for our department) ].

To my personal situation and KDevelop development:
Some of you know that apart from working here I'm studying, too. So 
unfortunately from 11th March I have to suspend my work on KDevelop for 
a half year. (Or lets say strongly limited on the needs of our department).

Conclusion:
I will jump up again on a branch depending on the needs of our institute 
and of the persons in it and I think it will be a version for KDE 2 at 
least for half a year.


Ciao

Walter


F at lk Brettschneider wrote:

>Hi,
>
>I want to the suggest to change our development and release policy after
>the 2.1 release:
>
>1.) If people develop for KDevelop-2.2, they will do that on cvs branch
>KDEVELOP_2_BRANCH. All KDevelop-2.2.x cvs release tags will be set on
>KDEVELOP_2_BRANCH. This branch is KDE 3, only. Roland will synchronize
>this branch with KDE_2_2_BRANCH again in a way that KDEVELOP_2_BRANCH
>continues the current development state.
>
>2.) If there will be KDevelop-2.1-bugfix-versions (2.1.1, 2.1.2, ...),
>their cvs release tags will be set on KDE_2_2_BRANCH. This means
>KDE_2_2_BRANCH is for bugfixes of 2.1, only - no new features as a
>version 2.2 would mean. This branch keeps on being a KDE2 branch with
>the ability to be source-compatible to KDE 3. As we do at present. This
>would mean, we do not accept feature patches for KDE_2_2_BRANCH any
>more. This branch should be closed for further development.
>
>3.) Gideon on HEAD as usual.
>
>Please discuss!
>
>Ciao
>F at lk
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>_______________________________________________
>Kdevelop-devel mailing list
>Kdevelop-devel at barney.cs.uni-potsdam.de
>http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-- 
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W._Tasin,_FB_04,_FHM-------------------PGP-KeyID:0x7961A645---:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>