Ext JS 4.1 - Updates

[lorezyra]

few weeks to get the pr2!!OMG
so when can we expect the final 4.1??

if thats true that will screw our whole project..all efforts and time spent in it so that we wouldnt be able to lunch in time!
im soo frustrated

I hate it when I can't "lunch on time!"


Never, ever, expect hard-line, written in stone Dates of Release from Sencha... If you base your project off of the latest release dates, your project will either fail or completely miss the deadline.

[_matias_]

@lorezyra,

forgive me if I misunderstand you but you seem to imply that it is buergi's or astrocybernaute's expectations that were unreasonable. Though in hindsight you seem to be right about this, there should be, between the current mess and a perfect platform, ample space for a release that is at least deployable for IE, Chrome and FF business cases while waiting for improvements to roll in.

In my case, I have been evaluating ExtJs 4 for 8 months, having to reassess my evaluation all the time since the platform is moving all the time. Thankfully, it seems to be moving forward, even though this might not be the opinion of those mainly interested in how its performance compares with that of ExtJs2 and 3. I can be thankful that the approval of the big assignment I am preparing for, has been put off month after month just like the decision for me of whether to go with ExtJs or not.

It seems you are right about the risks of taking Sencha's release dates without, I would say, at least 6 months' worth of salt. Up to the limit of the failure of one's project, it is better to wait than to get something not quite right quickly, but Sencha should make very clear right now to every prospective client that they might not have anything ready before several months

[buergi]

We waited at least 6 months, before we started to use Ext JS 4.0.7.

To call this an official release is an insult to everybody. They have still over 100 critical bugs... Hello????

[ykey]

Updates:

Today we have 107 active bugs. This past week our incoming bug rate is very close to our bug fix rate, and we are expecting the incoming bug rate to decline.

Also, I have attached a list of bugs that we are addressing for Beta. This is a working document so it changes. We'll publish a final bug list once the beta build becomes stable.

I am hoping that we will get a weekly update to this to help us get an idea of their pace on 4.1

[Edmund]

Our beta bug count continues to be high, about the same level as last week, at 105 bugs. Stability is still an issue. I’ve attached the bug list as a reference. Keep in mind that this is a working document and subject to change.

We heard the request for another preview, and the team is evaluating that option. We will let you know once we make that decision. Our main concern is not to get distracted from our goal of releasing a public beta.

Regarding release timeline: 4.1 GA will not be available before the end of the year. We currently do not have an estimate because our main focus is to get a stable 4.1 beta out. And we will release a beta as soon as we knocked down all the instability bugs.

[tvanzoelen]

stable 4.1

Now you're talking.

[zombeerose]

@Edmund

Thanks for the follow-up!

What is the probability of getting SVN access to the 4.1 branch?

Access to Development SVN

[Edmund]

@zombeerose
There is currently a bug blocking SVN build. It's one of the 105 unresolved bugs that we are tracking for the beta:
EXTJSIV-4327 building from SVN fails

[scottmartin]

There is currently a bug blocking SVN build. It's one of the 105 unresolved bugs that we are tracking for the beta:
EXTJSIV-4327 building from SVN fails

I believe the question at hand is when will we get access to the SVN/GIT, not what version currently exists. Access has been non-existent for ExtJS4

Regards,
Scott.

[rich02818]

@zombeerose
There is currently a bug blocking SVN build. It's one of the 105 unresolved bugs that we are tracking for the beta:
EXTJSIV-4327 building from SVN fails

It isn't necessary to be able to do a build to benefit from access to SVN. The ability to see what changes are made against the various bugs/issues can be very valuable....not to mention such access has been paid for by many of us. There is no unsolvable technical reason to hide the source code, it must be a management decision.