2.1: Memory leaks and bugs

Let view things in a different way. Version 2.1 is better than the 2.0, that is better than the 2.0 FC... and so on.

The 2.1 fixed many important bugs. People out there are using FCKeditor so this update is needed and highly recommended.

We have already discussed it before... every software has bugs, but Open Source has the bug list available to everybody.

We have to be concentrated on critical bugs to make the editor stable enough to be used on production site. This is the case of the 2.1

The memory leak problem has had a progressive evolution. It started with 6Mb (not acceptable)... decreased to 3Mb... and now we have less than a megabyte (acceptable). Of course there is still work to be done for it. Let's remember that the memory leak is a know bug in IE... What should we do in this case? Stop using IE?

Also, we are talking about Open Source... so, you can also help us solving the problem. Try to find solutions for the problems. Or, you can also sponsor specific developments. This is another way.

Regards,
FredCK

I second Frederico on this.

It's important to release a new version, when a lot of bugfixes have been made. That way the existing user base can work better. (Even when there are still bugs)

Second this also helps finding regressions with the bugfixes.

Third: Also the new functions can help some users. (But of course also may introduce new bugs)

The alternative would be to do a feature freeze, then a complete alpha/beta/rc test cycle. And such a cycle uses much time, so that you would have to stay with 2.0 for several months.


I think you should not too much focus on the version numbers. You could also tell the 2.1 release a 2.5 Alpha 1 version, or 3.0 Alpha.

The important thing is: Does the software solve my problem or not. And the 2.0 and 2.1 releases definitively do for a lot of users.