1. #21
    Sencha Premium Member
    Join Date
    Jan 2009
    Posts
    339
    Vote Rating
    110
    firefoxSafari is a glorious beacon of light firefoxSafari is a glorious beacon of light firefoxSafari is a glorious beacon of light firefoxSafari is a glorious beacon of light firefoxSafari is a glorious beacon of light firefoxSafari is a glorious beacon of light

      0  

    Default


    Good question.

    I see the docs have been updated to point to 4.2.2, so hopefully it's officially released?

    http://docs.sencha.com/extjs/4.2.2/
    -->

  2. #22
    Sencha - Support Team
    Join Date
    Feb 2013
    Location
    California
    Posts
    4,055
    Vote Rating
    69
    Gary Schlosberg has a spectacular aura about Gary Schlosberg has a spectacular aura about Gary Schlosberg has a spectacular aura about

      0  

    Default


    Should be in the support portal very soon.

    Update: The new releases are now available in the support portal.
    Last edited by Gary Schlosberg; 1 Oct 2013 at 9:01 AM. Reason: update


    Are you a Sencha products veteran who has wondered what it might be like to work at Sencha? If so, please reach out to our recruiting manager:
    sheryl@sencha.com
    -->

  3. #23
    Ext JS Premium Member mcouillard's Avatar
    Join Date
    Jun 2008
    Location
    Bucks County, PA
    Posts
    104
    Vote Rating
    11
    mcouillard will become famous soon enough

      0  

    Default


    Got it. Unfortunately stable 4.2.2 appears to be from a nighly near September 18, given the minor version number. I guess that's why I was seeing reference to 4.2.3 already, because the nighlies for 4.2.2 have really been for 4.2.3 for weeks.

    Code:
    Build date: 2013-09-18 17:18:59
    var version = '4.2.2.1144'
    -->

  4. #24
    Sencha User
    Join Date
    Nov 2008
    Location
    Lyon, France
    Posts
    223
    Vote Rating
    29
    christophe.geiser has a spectacular aura about christophe.geiser has a spectacular aura about

      -2  

    Default


    Quote Originally Posted by mcouillard View Post
    Got it. Unfortunately stable 4.2.2 appears to be from a nighly near September 18, given the minor version number. I guess that's why I was seeing reference to 4.2.3 already, because the nighlies for 4.2.2 have really been for 4.2.3 for weeks.
    ... one additional argument for a public ExtJs github repository
    C.
    -->

  5. #25
    Sencha - Support Team
    Join Date
    Feb 2013
    Location
    California
    Posts
    4,055
    Vote Rating
    69
    Gary Schlosberg has a spectacular aura about Gary Schlosberg has a spectacular aura about Gary Schlosberg has a spectacular aura about

      0  

    Default


    Yes, it looks like 4.2.2.1144 was the latest build pinned by QA. I'm told that because of this the release is rarely the very latest nightly. Apologies for any confusion.


    Are you a Sencha products veteran who has wondered what it might be like to work at Sencha? If so, please reach out to our recruiting manager:
    sheryl@sencha.com
    -->

  6. #26
    Sencha User
    Join Date
    Aug 2012
    Location
    Slovakia
    Posts
    1
    Vote Rating
    1
    terezka is on a distinguished road

      1  

    Default


    To make it clear: 4.2.2 release will be available only to Sencha Support subscribers or to public? Thanks.
    -->

  7. #27
    Sencha Premium Member
    Join Date
    Feb 2011
    Location
    Amsterdam
    Posts
    57
    Vote Rating
    6
    sblommers is infamous around these parts

      0  

    Default


    4.2.2.1144 is not sufficient so don't bother with that one.

    TBH i don't think they are ready to release just jet. IMHO 4.2.2 will never be released as GPL but that's just speculation ofc. 4.2.3 is on it's way tough, might be able to snatch that one as a GPL release maybe this month, who knows.

    I don't feel comfortable with Sencha any longer, no milestones to pin on, it's all too quiet

    For those interested: no change in nightlies since September 24th
    -->

  8. #28
    Ext JS Premium Member sumit.madan's Avatar
    Join Date
    May 2009
    Location
    Bangalore, India
    Posts
    121
    Vote Rating
    24
    sumit.madan has a spectacular aura about sumit.madan has a spectacular aura about

      2  

    Default


    Personally, I'm a little frustrated with the Sencha release cycle. I've started treating the stable releases as beta. I've tried to keep up with latest versions because it becomes a pain to upgrade it later, and even minor updates to the releases break down the application. So, I'm constantly in a debugging mode, and waiting for the bugs to be fixed before tooling any major features. To confuse it further, the bug fixes are only available to the support subscribers and everyone else is left hanging till the next public release, which in turn breaks down some other functionality, and the cycle starts all over again.

    I know that this topic has been discussed several times, but I just wish it was simpler to manage it and upgrade it in my application.
    -->

  9. #29
    Sencha User aw1zard2's Avatar
    Join Date
    Sep 2009
    Location
    Dallas, Texas
    Posts
    577
    Vote Rating
    32
    aw1zard2 has a spectacular aura about aw1zard2 has a spectacular aura about

      2  

    Default


    One issue I've seen on the forums is a lot of users are still using the low level javascript coding that you use with JQuery and others to get beautiful results. With Ext JS you need to learn to flow with the library. I've found bugs in the library but i also pinpointed where the issue was either my code or Sencha's code. If it was a bug in the library I gave details and where exactly the issue is for them. I have even posted a screenshot of firebug results.

    The company I work at we are currently replacing our Ext JS 3.4 architecture to 4.x. But I had something working since 4.0.2 and when I upgraded each time the library updated I had little issues that only took me a day or 2 to fix it. And just to let users know our software isn't a small one.

    We currently have close to 1,000 screens in Ext JS 3.4 with grids that get into millions of rows for a single grid.

    It's your choice to buck the system provided or go with the flow they are providing.

    I've been using Ext JS since 2.0 I'm used to having to rewrite everything to work with the library.
    In fact right now I'm working on rewriting everything we had in 3.4 to 4.2.2. But I see it as a way to cleaning out old overrides we had and clean up our code from developers that may not fully understand javascript.


    Of course this is just my opinion you can take it however you want to take it, it is not any disrespect to anyone. Just what I've noticed reading forum posts.

    Peace,
    -->

  10. #30
    Sencha Premium Member
    Join Date
    Feb 2011
    Location
    Amsterdam
    Posts
    57
    Vote Rating
    6
    sblommers is infamous around these parts

      2  

    Default


    Glad to hear someone that is happy with the way it is going on. I'm also from the 2.x branch. To be honest you make it sound like you take out of the box examples and work on them. Or maybe you need to clarify the 'flow' you are talking about.

    In my experience it's those corner cases that just don't work. 1 deviation from the example or 1 extra mixin and 1 nesting too many and stuff is broken. They are fixing it yes but with every build it seems another one pops up, that's what irritates people. And yes fixing it yourself might be a solution. I've fixed some very complicated stuff in the 4.2.2 branch from which i know for certain that not anybody could fix.

    We all send bug reports in but never hear anything about it for a pretty long time. Something is missing here that Sencha needs to hear pretty bad but they won't listen. Most parts of the forum are totally ignored.

    1) Bug report - tracking system (screw licensing this just needs to be there)
    2) Milestones milestones milestones
    3) Fixes to bugs number 1 priority

    Currently i still have 30 overrides standing that with every nightly build are still needed even when the release notes say they fixed it,... that's just annoying.
    -->