On Dec 18, 2009, at 11:21 AM, Bart Gauquie wrote:
Hi,
The point I'm trying to make is that even on an alpha release,
There is no release yet!
everything that worked before should still work perfectly. The new stuff being added are first buggy; seems normal to me. But if the new stuff is breaking old, working stuff, and we only notice it after a month; then it will take us a lot of time, debugging the issues, investigating them; time we should spent instead on adding new stuff.
The old stuff is *very very bad*. It needs to be fixed. This is when stuff breaks.
|I've done a number of production applications in Squeak and we always |used the stable version for that. Or, in case we really needed something |from the trunk version, we only updated occasionally when we were sure |it had reached a somewhat stable plateau.
You're correct on this one, however in this case, Pharo IS the production work. It is Pharo itself we are also developing. And since it is development, I think we should make sure the quality keeps up at a highest level possible, even if modifying it.
I don't mean to criticize, I love the opensource initiative that Pharo is, I'm just trying to help Pharo further. Any other thoughts on this?
I can not work on a system where every change on the unstable branch is garanteed to not break anything. That is because I don't know how this is possible to do. Marcus