Even if you migrate from 4.1.x to 4.1.y extjs may require you to rewrite some (a lot?) of your code.
So I wouldn't expect it to be easy
From the projects I've had going from 4.0.0 and eventually to 4.2.2 (upgrading with each release) I would disagree with this statement. Sure there were some bugs in some releases (4.2.1 had quite a few) but as for upgrading framework versions I had very little issues.
It really depends on how you code using Ext JS library.
If your doing a lot of overrides then yes it can be a headache.
My team and I work with the library then only if it is needed do we do an override.
We started our work of rewriting our Ext JS 3.1.1 architecture back when 4.0.2 was out.
With each new release we spent time no more than half a day fixing any issues that came to be.
When we went from 4.0.7 to 4.1.1 it only took me 2 hours to fix any issues. It took me even less time to move things to 4.2.2. But to each their own world, we had no overrides to begin with so debugging and fixing issues are easy.
With 4.2.2 I have a total of 3 overrides that we need because of having to support IE7/8 in my company.
The main thing that helped us was not to rewrite the library with code or overrides but study what the library was doing and make our architecture for screens based on that.
I'm waiting on the public beta of Ext JS 5.x so I can see what issues we have. From different talks I've had with Sencha devs I doubt I will have to change much to get it to work.
Just some simple stats about our main project:
Browsers supported officially: IE7/8 only
Browsers supported unofficially: IE9/10/11, Firefox, Safari, Opera, and Chrome
# of unique screens/views: several hundred total
We of course don't have all the screens/views moved over to 4.2.2 but from the few random screens/views I updated, it was easy to get them working.
As I tell the programmers at my company you can go with the flow of how Ext JS library works or you can try and paddle upstream of raging rapids by going against the library, your choice.
There isn't a lot of API changes and for the most part the upgrade should be easy. There are new features and such that rewriting some code to take advantage of may be required of course.
This is dependent on how much custom stuff and overriding you are doing so there isn't a solid answer to give but the API is largely the same.
The charts is an area where the API has changed a bit.
Thank you for your answer Mitchell.
Of course my question is not so easy to answer... but as I'm going to build a new (empty) project with ExtJS 4.2.2, what would you suggest to me as "development guidelines" to be ready for the switch to 5.x?
As I see the first one could be "do not override a lot", couldn't? Others (if any)?
I know everybody asked before and you don't know exactly the answer, but I will ask you anyway
Could we see 5 version in this month?
As you can compare 4.x to 5.x versions, do you think the first release of 5.x will be enough stable to go in production environment? or maybe it will be better to use 4.x?
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."