Thanks for your response,
Well, maybe it's just a permissions thing now...
After Ed's post this week, I started monitoring the:
First the ext-4.1.x branch returned 403, then the day after Ed's post, the ext-4.1.x branch returned 200, but was empty.... then the svn rev jumped from ~1400 to 1548, so I thought the mirror script was run, but now the ext-4.1.x branch is returning 403 again.... I've also tried ext-4.1.0, ext-4.1, ext-4.x, etc without luck...
The info in the SVN Access inside Sencha Support, still points to: For Ext4
And https://svn.sencha.com/ still points to the pre-git migration svn...
So, there is no info on where/how to access the 4.1 branch...
Maybe I'm just trying on the wrong url, or maybe when the mirror script where run the permissions where lost... dunno...
Thanks again for all your help on this
Can someone properly set our expectations on this? Reading back through the thread would have us believe that this should have been done weeks ago.
I am told the correct SVN branch for 4.1.0 beta 1 is:
Thanks again for the info Mitchell,
Just wondering... by looking at the branch name (that looks more like a tag)....
So, this means that we'll have to get thru all this problem again for beta-2/beta-X, rc-X, and then for each point release ? I thought that this would mean that we would get access to an at least 4.1.x branch... (was hoping for a 4.x so, going thru all this at least wouldn't be so frequent...)
What's on this branch that's not included on the beta-1 zip that was available for download some weeks ago ?
Are the development (and the fixes that have been fixed as reported on these forums after the beta-1 release) for beta-2 or rc-1 or whatever the name of the next 4.1 release would be, done on this ext-4.1-beta1 branch ?
I hope that the impression that I got by that branch name is simply a misunderstanding on my part, because, right now, if I'll have to wait for BETA-2/RC-1, final and so on to get the fixes, and then ask again for access to those branches, well... I really don't understand what value added as a paying support subscriber I'm getting in comparison of the free users... (without entering on the debate that it is a feature that's advertised on your support subscribers benefits)...
With that said... I'm REALLY happy with the beta-1, at least on my app (that was refactored a lot trying to minimize 4.0.x perf problems) feels way way better...
Originally Posted by mitchellsimoens
I can confirm that svn access for beta1 is working.
However, I am concerned that I don't see any changes made to the beta1 branch since 1/4/12. What is the tangible value of the advertised "SVN Access" feature? If beta code should not break the API, then why do we not have access to beta 2 already in order to get quick patches, such as this CSS error? Will this same cycle of asking for SVN access have to be repeated for beta 2?
Geesh... I had forgotten how painful it was to use svn. You guys upgrading to git any time soon?
Was trying to dig around for evidence of bugfixes, but the commit log isn't revealing much.
one commit creating the branch on the 4th at 10:21am ( more than a week after the beta1 release? )
and one by "root" with no message 9 minutes later. Thats it.
Suggestions for how to see bugfixes via svn? or does this mean there aren't any yet?
I feel that support subscription is not worth anymore. I see no difference between premium member vs regular customer except access for premium forum. Sencha, please do something about this.
Things are great before in Ext 3 time where the code is updated daily basis, living in bleeding edge development. We know the risk, don't care about it. I see Ext 4 development is very slow compared to previous release. Support is sucks. Last year, the so called Sencha Renewal Specialist convinced me to renew my subscription in order to get support for Ext 4, but with couple month left for my subscription to expire, I get nothing as a support subscriber.
The worst part is, Sencha new support model requires the support subscription remain continuous, so the date of expiration will be backdated in case of late renewal. WTF. Sencha software is great but I'm kinda disappointed of what Sencha do to us, a paying customer.
Originally Posted by maksimenko
We are discussing a better way to do this internally.
1. As was pointed out earlier, the last activity on the branch was on the 4th. How often should we expect this branch to be updated?
2. The README file says that in order to build from the branch we need a tools directory. That directory does not exist. I tried just running the build command but didn't get very far. How do we build?
3. Are there any up to date release notes, or change log?
Can somebody from Sencha give an update on this? The 4.1-beta branch has yet to be updated in 3 weeks now, so we are obviously not dealing with the current branch. As somebody asked earlier, what is the point of the support subscription if we do not have the ability to have the latest changes? We paid a lot of money to specifically have that ability.