As part of the upgrade of myVersionControl with new features, a new control panel and other enhancements we are streamlining the product range and increasing the amount of space. We will be doing this progressively to coincide with the release of the new interface however we have immediately increased the space on our base products:
The free account - now named 'Personal' has had a space increase from 4 MB to 100 MB.
The 50mb account - now named 'Team' has had a space increase from 50 MB to 500 MB
In order to maintain business viability we have put some reasonable restrictions on the numbers of users and projects that each product can accommodate. No paying customer will be adversely affected by this change, if you are currently exceeding the permitted numbers of users and or projects for your package you will not be forced to upgrade.
We are very excited about these changes that are occuring at myVersionControl which will help us continue to innovate and give our customers the very best in service and functionality.
Trailing slashes, Subversion Repositories and Subclipse
Trailing slashes on URLs are a tricky beast. Best practice dictates that when a web url does not have a trailing slash the browser is referring to a file, with the slash we are looking for a directory - see Slash Forward (Some URLS are Better Than Others by Waferbaby). We at myVersionControl are aware of this and as a matter of course rewrite a repository url without a slash to one that includes, for example:
https://company.myversioncontrol.com/subversion/repository1
would be rewritten as:
https://company.myversioncontrol.com/subversion/repository1/
Now it can be argued that 'repository1' is a directory or a file depending on what you consider subversion to be, however from the filesystem's point of view it is most definitely a directory.
It came to our attention recently that there are a minority of SVN clients that were struggling to cope with this trailing slash. For example Subclipse from Tigris would fail spectacularly.
In order to remain compatible with as many clients as possible we have changed our configuration protocols to accept your repository urls with or without the slash. If you have any problems with any other clients then as ever let us know!
https://company.myversioncontrol.com/subversion/repository1
would be rewritten as:
https://company.myversioncontrol.com/subversion/repository1/
Now it can be argued that 'repository1' is a directory or a file depending on what you consider subversion to be, however from the filesystem's point of view it is most definitely a directory.
It came to our attention recently that there are a minority of SVN clients that were struggling to cope with this trailing slash. For example Subclipse from Tigris would fail spectacularly.
In order to remain compatible with as many clients as possible we have changed our configuration protocols to accept your repository urls with or without the slash. If you have any problems with any other clients then as ever let us know!
Sneak preview of the control panel upgrade
The redesign and upgrade of the main MVC web control panel is well underway. The focus is largely on usability and creating a framework and structure that will allow us to introduce the new features we are working on like repository browsing and hooks and third party resources management. This would be difficult in the existing structure.
The new site will make fairly extensive use of client side scripting techniques involving numerous Ajax calls, drag and drop and pseudo modal windows. This is all aimed at making the control panel behave more like a console application and to improve the overall usability and configurability of subversion. Non JavaScript enabled browsers will be redirected to the existing control panel until we complete the redesign of the basic accessible version. We also have plans to introduce slimed down versions of the control panel for mobile devices, primarily so administrators can keep an eye on development progress from wherever they are.
The new site is being tested daily in IE 7 & 8, Firefox, Safari, Opera and Chrome. Users of other browsers will be given the opportunity to view the site using the old (well, current for now) control panel.
Release of the new control panel is on schedule for release in the last half of June 2009.
The new site will make fairly extensive use of client side scripting techniques involving numerous Ajax calls, drag and drop and pseudo modal windows. This is all aimed at making the control panel behave more like a console application and to improve the overall usability and configurability of subversion. Non JavaScript enabled browsers will be redirected to the existing control panel until we complete the redesign of the basic accessible version. We also have plans to introduce slimed down versions of the control panel for mobile devices, primarily so administrators can keep an eye on development progress from wherever they are.
The new site is being tested daily in IE 7 & 8, Firefox, Safari, Opera and Chrome. Users of other browsers will be given the opportunity to view the site using the old (well, current for now) control panel.
Release of the new control panel is on schedule for release in the last half of June 2009.
Repository overview showing colour coded repositories, head revision number, time of last commit, last user and size of repository.
Repository detail page, showing label colour chooser (changes colour of heading and some other page assets depending on which page you are on).
Repository detail shows log message, commiter and a count of the files in the changeset. Clicking the number drops down details of the changeset which will ultimately hyperlink to the repository browse/diff feature.
The page also includes and option to stream commit information (useful on active projects with multiple commiters).
Security page. We spent a lot of time on this page trying to make it as intuitive as possible. The screenshot shows two securable resources (Subversion repository and associated Trac instance). Users are added to the root of the resources and their permissions configured from there. We will also be adding the ability to set advanced permissions on folders within your subversion repository. In this case there will be the added dimension of inherited permissions to display.
The screen shot also shows the repository drop down menu allowing quick changing between repositories.
Server Upgrade to Subversion 1.6.1
The latest version of Subversion (1.6.1) is now available on our servers. This provides a number of new features which myVersionControl customers may now take advantage of.
We have not automatically upgraded your repository to the latest version. This is because it may lead to the repository being innaccessible to your older subversion tools. You repository will work fine without upgrading but in order to take advantage of the latest 1.6.1 features you will need to upgrade both your client and repository.
Upgrading your repository is very simple. Go to your project admin page in the control panel, choose a project and select "Project Resources". Choose the upgrade option (see picture) and click Update. You are now upgraded!
New repositories are automatically created as version 1.6.1.
Subscribe to:
Posts (Atom)