PDA

View Full Version : Access to 4.1 svn/git branch?



maksimenko
1 Nov 2011, 1:18 PM
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
2 Nov 2011, 11:53 AM
Yeah .. what he said!

Regards,
Scott.

terrycursh
2 Nov 2011, 5:46 PM
so thats what I wanna say too~

kanntronics
16 Nov 2011, 4:02 AM
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
1 Dec 2011, 12:30 PM
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
1 Dec 2011, 1:23 PM
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
7 Dec 2011, 5:59 PM
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
12 Dec 2011, 12:29 PM
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
12 Dec 2011, 12:34 PM
Once 4.1 beta 1 is out, it should be put into SVN... which isn't that far off.

george4isvy
14 Dec 2011, 2:48 PM
What about fixes for specific bugs? I'm running up against the one documented in the following forum post:
http://www.sencha.com/forum/showthread.php?139631-Panels-sometimes-disappear-when-their-siblings-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?

mitchellsimoens
14 Dec 2011, 3:03 PM
What about fixes for specific bugs? I'm running up against the one documented in the following forum post:
http://www.sencha.com/forum/showthread.php?139631-Panels-sometimes-disappear-when-their-siblings-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?

Hold on for a couple more days... not saying anything but I'm saying something

george4isvy
15 Dec 2011, 3:40 AM
Ok....not thanking you, but I'm thanking you ;)

maksimenko
24 Dec 2011, 2:32 PM
Hello there,

Happy Holidays for all!

I'm just wondering, now that 4.1 Beta is out... are we able to finally access the code repository ? so we can test the latest fixes for the bugs that were reported on the beta?

I've tried changing the branch from ext-4.0.x to ext-4.1.x, ext-4.1, etc but all returned forbidden access....

Thanks again

edspencer
28 Dec 2011, 8:49 PM
@maksimenko I'll follow up with the team on that, it should be open now that we are in beta. If there's some access problem we'll try to get it fixed asap

scancubus
29 Dec 2011, 8:23 PM
Can you guys turn this back on. I would agree with the other paying subscribers that we should have immediate access to the SVN. We have all been waiting a long time for this new makeover for 4.x. We have all had a lot of explaining to do to our users, so it would be great to get access.

Thanks!

edspencer
29 Dec 2011, 8:27 PM
Can you guys turn this back on. I would agree with the other paying subscribers that we should have immediate access to the SVN. We have all been waiting a long time for this new makeover for 4.x. We have all had a lot of explaining to do to our users, so it would be great to get access.

Thanks!

Agreed! I'm on the Sencha Touch team at the moment so bear with me... as I see it we should be able to open this up properly shortly

edspencer
2 Jan 2012, 5:10 PM
We should be able to roll this back out tomorrow, thanks for your patience

lagnat
4 Jan 2012, 12:50 PM
+1

maksimenko
6 Jan 2012, 3:05 PM
Any news on this ?

Thanks again

mitchellsimoens
6 Jan 2012, 3:10 PM
I'm told it should be in there.

maksimenko
6 Jan 2012, 3:22 PM
Hi Mitchell,

Thanks for your response,

Well, maybe it's just a permissions thing now...

After Ed's post this week, I started monitoring the:

http://svn.sencha.com/svn/sdk/branches/ext-4.0.x/ and
http://svn.sencha.com/svn/sdk/branches/ext-4.1.x/

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
http://svn.sencha.com/svn/sdk/branches/ext-4.0.x
(http://svn.sencha.com/svn/sdk/branches/ext-4.0.x)
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

lagnat
11 Jan 2012, 10:47 AM
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.

mitchellsimoens
11 Jan 2012, 12:02 PM
I am told the correct SVN branch for 4.1.0 beta 1 is:

https://svn.sencha.com/svn/sdk/branches/ext-4.1-beta1/

maksimenko
11 Jan 2012, 12:48 PM
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...

Thanks again



I am told the correct SVN branch for 4.1.0 beta 1 is:

https://svn.sencha.com/svn/sdk/branches/ext-4.1-beta1/

zombeerose
11 Jan 2012, 12:56 PM
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 (http://www.sencha.com/forum/showthread.php?170663-4.1-B1-CSS.createStyleSheet()-error)? Will this same cycle of asking for SVN access have to be repeated for beta 2?

:(

dnorman
11 Jan 2012, 2:22 PM
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?

kanntronics
11 Jan 2012, 7:01 PM
+ 1

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.



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...

Thanks again

mitchellsimoens
12 Jan 2012, 5:56 AM
We are discussing a better way to do this internally.

lagnat
12 Jan 2012, 11:22 AM
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?

Thanks..

kevhender
23 Jan 2012, 8:38 AM
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.

mitchellsimoens
23 Jan 2012, 8:39 AM
We are discussing a better way to do this internally.

We are still working on it.

mitchellsimoens
23 Jan 2012, 8:54 AM
Until we get something like svn or git or something better for a permanant solution... if you log into support.sencha.com you should see a Nightly Builds link in the Latest Build box.

30905

Once again, hopefully we will get a more permanent solution but until then this, at least, gets you the latest code. You also get a changelog dump I believe.

rich02818
23 Jan 2012, 11:59 AM
The 'nightly builds' link does nothing...

How is internal scm being done? Why is it so hard to provide access to the current soure baseline?

mitchellsimoens
23 Jan 2012, 12:03 PM
The 'nightly builds' link does nothing...

How is internal scm being done? Why is it so hard to provide access to the current soure baseline?

Dang... didn't test it but this is where the snapshot will be, core devs are flying into california today for this week so the build may not have been run.

The translation between git and svn is a manual process.

rich02818
23 Jan 2012, 12:10 PM
It isn't like this is a new issue. Sencha announced a switch to git (http://www.sencha.com/blog/ext-js-is-migrating-to-git/) in Feb 2010 and Ed said

"First of all, keeping compatibility with svn is of upmost importance to us. Everyone with a support subscription will still have access to the latest commits. Although we are developing the code with Git, every commit is mirrored over to svn.
...
The move to git is an internal choice we’ve made to help us easily manage our multiple source branches. While the main git repository is on GitHub, if we have support subscribers who would like to move from svn to git we can add a mirror on our servers with the same access permissions that svn currently has."

So why not just provide access to a git mirror?

kevhender
23 Jan 2012, 12:12 PM
Until we get something like svn or git or something better for a permanant solution... if you log into support.sencha.com you should see a Nightly Builds link in the Latest Build box.


This is very helpful, thanks Mitchell.

lagnat
23 Jan 2012, 12:15 PM
For whatever it's worth, it worked for me a couple of hours ago.


-rw-r--r--@ 1 me 1255282267 50716319 Jan 23 12:56 ext-4.1-20120122.zip

mitchellsimoens
23 Jan 2012, 12:17 PM
For whatever it's worth, it worked for me a couple of hours ago.


-rw-r--r--@ 1 me 1255282267 50716319 Jan 23 12:56 ext-4.1-20120122.zip


Thank you... once the dev that has this all set up lands I will ask him to look into this.

mitchellsimoens
23 Jan 2012, 12:17 PM
So why not just provide access to a git mirror?

Having our own git server is an option, one that we are exploring.

lagnat
23 Jan 2012, 12:21 PM
And I should point out that it's still working for me. Just checked it again.

mitchellsimoens
23 Jan 2012, 12:23 PM
And I should point out that it's still working for me. Just checked it again.

Interesting... Just tried with Chrome, Firefox and Safari on my Mac and the link for me is just the # symbol... the link for 4.0.7 works though

mitchellsimoens
23 Jan 2012, 12:27 PM
Ok... when in doubt clear cache and refresh and it works for me now..

30917

rich02818
23 Jan 2012, 12:36 PM
It is now working for me as well!

mitchellsimoens
23 Jan 2012, 12:43 PM
It is now working for me as well!

Fantastic! Like I said, this shouldn't be a permanent solution... it was just the fast thing to get the code to you. Git to SVN doesn't seem to behave very well at all so it's gonna take a little bit of time to get a firm solution and implement it. It is a priority even when we have two frameworks very close to big releases.

lagnat
24 Jan 2012, 8:12 AM
Related question.. what should we do about bugs that we find in the nightly releases? Is it proper to use the 4.1 beta and/or bugs forum for those?

mitchellsimoens
24 Jan 2012, 8:57 AM
Related question.. what should we do about bugs that we find in the nightly releases? Is it proper to use the 4.1 beta and/or bugs forum for those?

Will get an answer for you today on this. It is kind of use at your own risk but if a bug is found from a change then it would be nice to get rid of it fast... maybe just if the bug is in a couple nightlies then it could be a bug but I will be asking for more clarification on this and will get back to you.

mitchellsimoens
24 Jan 2012, 10:04 AM
Looks like nightlies are not supported and are use at your own risk. We will be putting up a disclaimer to say this. However, if a bug remains for more than a week, I would think it should be safe to say it is a bug... just don't want false positives.

kevhender
8 Feb 2012, 5:50 AM
Looks like nightlies are not supported and are use at your own risk. We will be putting up a disclaimer to say this. However, if a bug remains for more than a week, I would think it should be safe to say it is a bug... just don't want false positives.

Hey Mitchell, are these nightly builds really the very latest code for 4.1 beta3? I have been monitoring several bugs that have been marked as "fixed" that are still not working correctly using the nightly builds:

http://www.sencha.com/forum/showthread.php?177623
http://www.sencha.com/forum/showthread.php?176903
http://www.sencha.com/forum/showthread.php?176886

(http://www.sencha.com/forum/showthread.php?177623)In fact, there doesn't seem to be any indication that the files that obviously need to be changed to fix these bugs have been changed. Is this really the latest and greatest every night, or is there another SVN branch that we're just not getting? Thanks.