Access to 4.1 svn/git branch?

[maksimenko]

Hello there,

Any chance we'll be getting access to the 4.1 svn (or preferrable git) branch soon ?

I miss the days when we could access the trunk or any 3.x branch without problem and get up-to-date fixes for the framework.

In 4.0, the svn mirror seems to be updated very sporadically, and even have problems (the line 98 in extjs/src/form/RadioGroup.js have a ">>>>>>> Fix @link in Ext.form.RadioGroup docs." line that needs to be commented out or removed so an svn build works) ... and now the 4.1 branch isn't even accessible.

I'd like to test the 4.1 but would prefer to have an up-to-date version whenever is possible, and more now with so many changes and fixes coming to the 4.1 branch (I migrated the app from 3.x a couple of months back but it's only available in "beta" fashion for a few clients that don't use IE, and have been waiting for the 4.1 branch so I can start testing and migrating whatever needs to be done for 4.1 and be able to use the new app on "production" for all my clients asap thus eliminating the need of maintaining two branches).

Thanks

[scottmartin]

Yeah .. what he said!

Regards,
Scott.

[terrycursh]

so thats what I wanna say too~

[kanntronics]

Sencha, please do something about this. Don't let us, a support subscriber down. It's very frustrating. No point of getting support subscription when I need to wait 4.1 release for bug fixes.

[mitchellsimoens]

Historically, we have tried to only allow the version that is beta. So when 4.1.0 beta comes out, it should make it's way to SVN. I'm sure you know that this is the bleeding edge code that is in SVN so it may be a bumpy road is some cases. Personally, I update my local git repo couple times a day and I have no problems I couldn't easily correct.

[maksimenko]

Hello Mitchell,

Thanks for your response. I'm really glad to finally hear that!. Hopefully the beta comes out soon enough....

And yes, no problem with it being bleeding edge code, etc. Fully understood that it's at our own risk. In any case, there's always overriding , and now easier to include/exclude with Ext.define overrides...

Lucky you that can update your local git a couple of times a day!

Thanks again.

[CasualNetworks]

Lack of 4.1 SVN and Diff's have made it hard to decide what features we focus on and what 'workarounds' we need to perform.

The statement that Mitchell makes rings true, but doesn't seem to coincide with the printed documentation

Reference: "Get Subversion Access"
http://www.sencha.com/products/releases

The fact that the public already has access to the Ext JS 4.1 PR1, just doesn't seem to fit well with support subscriber access and "constantly keep abreast of the latest enhancements and fixes" it references. No where within this page that I could find describes the scenario of a 'third' partially secret, but public snapshot available resource.

If your concern is 'support' then only allow bugs to be submitted on x,y,z versions. Don't restrict our ability to have access to information we need.

I would prefer access, but having a consistent messaging and information for paid subscribers helps us have the information at hand to make software direction decisions. Does that make sense?

[lagnat]

Lack of 4.1 SVN and Diff's have made it hard to decide what features we focus on and what 'workarounds' we need to perform.

This.

Please count my vote for early SVN access to 4.1.x.

[mitchellsimoens]

Once 4.1 beta 1 is out, it should be put into SVN... which isn't that far off.

[george4isvy]

What about fixes for specific bugs? I'm running up against the one documented in the following forum post:
http://www.sencha.com/forum/showthre...-are-collapsed

At the top of the forum post it says: "Looks like we've fixed this one. According to our records the fix was applied for EXTJSIV-3443 in 4.1.0"

As licensees/premium-members, is there at least a patch available to us?