Maintenance Releases??? 3.01? 3.02???

[aw1zard2]

I've always hated the back and forth arguments going on.

The issues are plain and simple if you spent as much time writing in these forums as you did fixing your bugs or searching for work-arounds with bugs already found you would have nothing to complain about.

Most of the bugs I find have work-arounds posted just have to dig for them. If not someone has hit it before so send them a pm about it. So please stop the crying and get back to coding please this is getting quite annoying.

I respect the license model in place and I'm not a svn user.

[Jubei]

Originally Posted by aw1zard2

I've always hated the back and forth arguments going on.

The issues are plain and simple if you spent as much time writing in these forums as you did fixing your bugs or searching for work-arounds with bugs already found you would have nothing to complain about.

Most of the bugs I find have work-arounds posted just have to dig for them. If not someone has hit it before so send them a pm about it. So please stop the crying and get back to coding please this is getting quite annoying.

I respect the license model in place and I'm not a svn user.

You do realize that thread reading is optional? If it bothers you...why read it...and worse yet...add a comment that adds no real value all while missing the original point?

I am sure that all of us could FIX the bugs ourselves...but that isn't really what is expected when you buy a commercial license now is it?

[iagui]

Originally Posted by aw1zard2

I've always hated the back and forth arguments going on.

The issues are plain and simple if you spent as much time writing in these forums as you did fixing your bugs or searching for work-arounds with bugs already found you would have nothing to complain about.

Most of the bugs I find have work-arounds posted just have to dig for them. If not someone has hit it before so send them a pm about it. So please stop the crying and get back to coding please this is getting quite annoying.

I respect the license model in place and I'm not a svn user.

If the discussion annoys you, simply don't read it, go back to your coding.

Obviously I have made my own workarounds for those bugs, but that's not the point here (although making workarounds is double work, because after a minor release you have to review al the bugfixes you've made to work with the new version, or remove them).

I also respect the license model, but a release like 3.0.3 doesn't fit in the GPL model.

[aw1zard2]

You mean GPL+commercial+support license model right?

[SonicBog]

I suspect that if ExtJS was a binary toolkit rather than Javascript, those in favour of waiting for infrequent Minor releases for bug fixes as opposed to frequent bug fix releases would have a different tune. The fact that ExtJS is javascripts gives you the opportunity to work around a problem (that you should not have to) where as a binary gives you no choice but to wait for a bug fix.

If you are forced to wait, then you expect the fixes to roll out quickly.
The fact that you can get into ExtJS to work around a problem does not mean that this is what we should have to do to get a component working. I am sure that my boss will ask ExtJS for some money when I log the fact that I have spent x amount of time fixing up ExtJS code to work around a problem as the next minor update with functionality and bug fixes is not due for several more months (future example).

He would also query my request for support when I tell him it is required in order to get the bug fix releases before the minor feature releases.

[MartiCode]

In the end the argument is pretty simple: you buy a software, you should be entitled to have it delivered bug-free, or at least have fixes for known bugs be released as soon as possible and at no extra cost.

From what I understand someone who buys a license even today will still only get 3.0.0, a version that is obselete and known to have bugs.

[mschwartz]

http://www.extjs.com/forum/showthread.php?t=83652

The developer releases are not well tested against all the programming the community here does with the library. It may not at all be what you expect to have access to these things. My experience is that something I wanted fixed was fixed in svn, but the state of the rest of the code, since it's in development for 3.1 release, actually regressed major sections of my application.

I found the company to be rigorous in how they released 3.0.0. They produced release candidates and let everyone try it out. They were quite open to looking into every bug report and fixed most things. They slipped the shipping date because it wasn't ready enough.

Let's give them some credit, eh?