Tag Archive for 'webinars'

Page 2 of 2

WANdisco’s April Roundup

Happy spring! As well as enjoying the warmer weather, everyone at WANdisco has been busy creating and launching a completely redesigned WANdisco.com. We think you’ll agree, it’s a major improvement on our old website:

With this update, we’ve concentrated on making the WANdisco website easier to navigate, and easy to use, with a section dedicated to what WANdisco is all about. Feedback? Suggestions? As ever, please don’t hesitate to contact us – we’re all dying to know what you think about the new-look WANdisco.com.

This month, we were lucky enough to co-host a webinar with our friends at CloudBees. ‘9 Ways to Dominate Development with Jenkins’ taught attendees nine Jenkins best practices that can be easily implemented to make your life – and the life of your team – easier. As if that wasn’t enough, the following week industry expert Adrian Bridgwater co-hosted our ‘Introducing Subversion Access Control 4.1’ webinar, looking at what’s new and noteworthy in the 4.1 release of our security product for Enterprise Subversion. We’re always announcing new webinars for the Subversion community – keep checking our Free Subversion Training Webinars for the latest information.

Users of Subversion’s 1.6 series got an update this month, with the release of Subversion 1.6.18. The full list of what’s new and noteworthy in this release is available in the Changes file and the binaries can be downloaded for free from our website. What’s more, uberSVN users can easily toggle between the latest 1.7 releases of Subversion and 1.6.18, using uberSVN’s ‘SVN Switch’ functionality.

There have also been major changes to uberSVN, the free, open ALM platform for Apache Subversion. With the release of 12.4 ‘Chimney House,’ uberSVN officially came out of beta! A massive thank you to everyone who has downloaded, deployed, and provided feedback on the beta release – we couldn’t have done it without you! As well as taking us out of beta, the 12.4 release introduced many new features, including:

  • New plugin API architecture and core upgrade that allows WANdisco registered plugins to work with uberSVN. We’re particularly excited about this one, as it lays the foundations for future uberSVN SDK releases.
  • Subversion Access Control’s 4.1 LDAP functionality (apart from some advanced features linked directly to Access Control) has been integrated into uberSVN’s ‘Default LDAP’ tab (accessible through the ‘Administration’ section.) This is the feature uberSVN users have requested the most.
  • A new file upload function has been added to the uberSVN Updates tab. This allows us to hand build updates for installations, push updates to users who aren’t connected to the internet, and deliver specialist packages to specific installations.
  • A new option to subscribe to our Latest Release Channel or wait for us to deliver fixes highlighted by our early adopters in a Stable Release Channel. Set your preference within uberSVN.
  • Plus, the usual list of bug fixes, including updates to the activity feed posts.

And, as is tradition, we’re all looking forward to celebrating the release of uberSVN Chimney House, in the venue it’s named after – The Chimney House at Kelham Island, Sheffield.

And in other uberSVN-related news, uberSVN turned one this month! uberSVN, the free, open ALM platform for Apache Subversion is now officially one year old. It’s hard to believe uberSVN has only been around for twelve months: not only has this unique, SVN-based product already been awarded the Made in Sheffield mark and Business IT Innovation of the Year medal, but it’s received a positive response from the community, and fantastic reviews by the IT media. We celebrated with some very special uberSVN cupcakes made by our friends at Fancie. We’re sure you’ll agree, they did a brilliant job!

Thank you for all your support over the past year – and happy birthday, uberSVN!

Free SVN Webinars: What do you want to see?

Are you getting the most out of the checkout command? SVN Checkout may be the most frequently used Subversion command, but it has many options you may not be aware of. The next webinar in our free Subversion training series will show attendees how to make full use of the checkout command and understand the messages it generates under different scenarios. In this one hour session, we’ll cover:

  • The usual work cycle
  • Required parameters (decisions)
  • Checkout depth issues
  • External folders
  • Nested folders
  • Batch checkout

Places are limited, so register now to avoid disappointment!

We may have just announced a new batch of webinars, but at WANdisco we’re always thinking ahead, and we’re already planning the next set of SVN webinars! We need your help to make sure we’re delivering exactly the content you want, so we’ve put together some short polls to find out what we should include in our next webinars.

Help us make our Subversion webinars even better, by completing our polls: What makes a good case study? and SVN and Continuous Integration.

Interested in Enterprise Training? We also offer a comprehensive list of SVN training courses, ranging from Core Concepts, to “train the trainer” sessions. More information is available at our Enterprise Training webpage.

Even More Free Subversion Webinars

We hope you’re enjoying our bi-weekly free Subversion webinars! After getting a great response from the community, we’ve announced the next few webinars in the series, including another webinar on branching and merging, as so many of you requested!

Here’s what’s coming up over the next few months:

  • Checkout Command – Although checkout is the most frequently used Subversion command, it has many options that few users are aware of. During this session, attendees will learn how to make full use of the checkout command and understand the messages it generates under different scenarios.
  • TortoiseSVN 1.7 New Features – Attend this webinar to learn all about the latest changes and get the most out of TortoiseSVN 1.7.
  • All About the Subversion Commit Command – Take a closer look at the Subversion commit command, including commit dialog options, unversioned files, changelists, and common problems and how to avoid them.
  • Introduction to Subversion – Back to basics! This course is intended as a primer for both new users and people who are thinking of making the jump to Subversion.
  • Version Control using Subversion – Learn a little more about the how and why we use version control; we will point out the advantages of version control, using SVN as an example.
  • Advanced Branching and Merging – This webinar will cover the meaning of merge messages, analyzing branches using revision graphs, using svn:mergeinfo and the different merge types (reintegrating a branch, merging a range of revisions, and merging two different trees.)

All these webinars are free, but places are limited. Register now to avoid disappointment.

Open Source Support and Training : Your Options

It’s no secret WANdisco are big fans of open source, but where do you go when you encounter a bug, or your open source project keeps throwing errors? In this post, we cover all the options available for open source fans in need of some extra guidance.

Community support

Successful open source projects are typically collaborative efforts between hundreds, if not thousands of developers. This collaborative development encourages transparent, archived communication through mailing lists and forums, which can be an invaluable (and free!) source of information for the open source user. And, if you can’t find the answer to your question, you can always post it at the project’s mailing list, community forum, or even Stack Overflow.

For Apache Subversion users, SVNForum.org is the place to go to connect with the SVN community. Sign up to discuss everything Subversion, and exchange information and tips with other users. Alternatively, the Subversion project maintains a series of active mailing lists, including the users mailing list where you can post build problems, configuration issues, usage questions, and more.

Professional Support

Open source solutions have plenty to offer, but many organizations are concerned about the level of support they can get from the community alone. Most open source projects have a great community of users who are always willing to help out, but mailing lists and forums aren’t always the ideal place to reach out to when disaster strikes your organization! Thankfully, many established open source projects now have professional support options.

When choosing a professional support provider, there are a few questions worth asking:

1. Do they have committers on the project?
2. Do they cover the hours I need? (of course, 24-by-7 worldwide support is always preferable!)
3. Are they enthusiastic about the project?
4. How easy are they to contact? Do you get a named support contact? Can you dial a number and speak to a real person?
5. Do they have customer testimonials?

As one of the major corporate sponsors of Subversion, WANdisco offer professional support for SVN. Our professional Subversion support includes:

  • Guaranteed response times.
  • 24-by-7 Worldwide coverage.
  • Indemnification coverage
  • Our Enterprise security product, Subversion Access Control
  • ….and more!

And, act before Friday (April 13th, 2012) to get the first 90 days of Subversion support for free, when you purchase any of our one year support contracts.

Enterprise-class support for TortoiseSVN is also available, alongside professional support for uberSVN, the open ALM platform for Apache Subversion.

Free Online training

Over the last couple of years, open source solutions have been gaining popularity within the enterprise, and with all the benefits of open source, it’s easy to see why! Of course, cost is one of the major reasons why organizations switch to open source. With closed source, there’s the initial outlay, but there can also be hidden extras; support charges, the expense of ongoing upgrades, training costs, etc.

With open source projects, not only are you saving on the software’s initial cost, but there’s typically plenty of tutorials, webinars, refcards and articles freely available on the internet, to help out with everything from the installation process, to best practices for the advanced user.

As part of our commitment to the Subversion community, we run bi-weekly free training webinars, covering everything from branching and merging, to running Subversion with continuous integration, hook scripts, and more.

Enterprise Training

Despite the wealth of resources freely available on the internet, there may come a point when an organization needs some formal training to get the most out of their open source software. Successful open source projects are frequently the subject of professional training sessions, but it may also be worth investing in ‘train the trainer’ sessions, so all future training can be performed in-house by your own staff.

At WANdisco, our Subversion training courses are designed to provide the essential hands-on experience you need to increase productivity. Choose from public classes at our training centres; private, on-site classes; and web-based training. Some of the courses we offer, include:

  • Core Concepts – covers architecture and design principles, branching and merging, conflict resolution, and more
  • Subversion for Administrators – gain the background knowledge needed to effectively install, configure and manage Subversion repositories and servers
  • Train the Trainer – designed for customers with in-house training staff

Branching Options for Development

Branching and merging is a contentious issue for the Subversion community, with even the most experienced Subversion users sometimes needing extra guidance on how best to manage their branches. In our latest webinar, Michael Lester, WANdisco’s Director of Training, provided an introduction to branching and merging which ranged from the basic, ‘what is a branch?’ question, to the different development models open to Subversion users, and advice on managing deleted branches.

Essentially, a branch is a line of development that exists independently of another line. Branches allow developers to work on code independently of the work going on in the trunk. No changes made within a branch are seen by people working in the trunk, or in any other branches. There’s no real limit on the number of branches that can be created, but there are some general development models for branching that Michael addressed in the webinar:

1) “Branching Nothing” Development Model

In this model, all of the development is done within the trunk. In ideal circumstances, all of the checkouts and commits will be in line, and no-one will check out the same thing at the same time, but it’s likely there will eventually be a situation where multiple people checkout the same code simultaneously, and then it becomes a race to see who can make their commit first. The second person to make their commit will receive a message alerting them that their commit has failed, and that they must update their working copy.

‘Updating the working copy’ takes the differences between what was checked out and edited, and what the other person has modified, and applies it to the working files. In the best case scenario, this is a straightforward update, but in some cases it can create a conflict situation.

The branching nothing model can create ‘update hesitation,’ where the developers are aware that performing a commit could force them to go back and deal with other peoples’ changes – a potentially time-consuming and annoying process! – which encourages them to wait until the last minute to make their commit. The branching nothing development model tends to get more complicated, the more people who are working on the same code, at the same time.

2) “Branch Everything” Development Model

With this development model, every change within a project is given its own branch; either a ‘bug branch’ or an ‘enhancement branch.’ People are assigned to work on a particular branch, and these branches are then merged into the trunk. This has a number of advantages:

  • All work is isolated. You don’t have to worry about other changes interfering with yours until the merge happens.
  • All work is scheduled. There is a defined branch for everything that needs to be worked on.
  • All work is branched from a stable trunk revision.
  • Small, independent merges mean it’s usually easier to resolve changes.

However, there are also some disadvantages to this development model:

  • Lots of branches.
  • Lots of merges.
  • A lot of overhead for some very straightforward fixes, e.g the misspelling of a word, or a column heading not being centered.

3) “Branch Big Things” Development Model

With this development model, every task is divided into one of two categories:

  • A small development effort – worked on directly in the trunk, with no branching or merging required!
  • A big development effort – tasks such as a complicated bug or enhancement are given their own branch.

This categorisation is based on:

  • Relationship to other bugs / enhancements – is the change likely to impact any other code?
  • How much testing is required? – some changes may require virtually no testing (e.g correcting a misspelt word) but other times you will literally have to do system-level testing to ensure the changes haven’t had any unforeseen negative effects.
  • How long will the bug/enhancement take?

Deleting Branches & Finding Deleted Branches

Regardless of whether you branch everything, or follow the ‘branch big things’ development model, if you’re going to branch, then at some point you’ll have to delete some of the old branches. Deleting branches is simply a matter of:

1) Go to the repo browser.
2) Right click on the branch you want to delete.
3) Select the delete command.

Remember that when you delete a branch, it gets deleted from the revision folder but not from the repository. You can always go back to an earlier revision to see how the branch looked, and have the option of exporting the code from the deleted branch, or recovering the branch and recreating it in a later revision.

To make it easier to locate a deleted branch, it is a often a good idea to write something in the log message upon deleting that branch. Another good idea, is to create a ‘deleted branch’ folder, where you can store branches that you no longer need.

Need more advice on branching and merging? The full webinar is available for replay now. Our next webinar, ‘uberSVN: Access Control Management’ will show you how to quickly setup access control for Subversion users and how to easily create repository access rules, allocate users to teams, and monitor team activities. The webinar will take place on October 27th, 2011.