Name Change

[Aleix]

Well, I think KDevelop4 intends to do the same as KDevelop so it should stay
as KDevelop. Feature parity doesn't mean the same as maturity.

I don't think the *4 point is really valid since KDevelop4 is just a
codename, the program is still called KDevelop. If you prefer we can make up
a codename as other programs do like many other projects do.

On Mon, Nov 3, 2008 at 11:09 AM, David Nolden <zwabel at googlemail.com> wrote:

> Hi guys! I know we've had the same discussion about a year ago, but looking
> at
> the comments to my last blog-post, I do believe now that we need a
> name-change.
>
> The problem:
> - People tend to measure KDevelop4 based on KDevelop3, although it's a
> actually completely new app. This means that people who found KDevelop3 too
> complicated won't try KDevelop4 as well.
> - People who did like KDevelop3 will expect the same functionality in
> KDevelop4, which he most probably is not going to get.
>
> I don't think this is a pressing issue right now, but it might make sense
> to
> consider this before our first stable release.
>
> Greetings, David
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20081103/bfbffde7/attachment.html>