Release announcement for RabbitVCS BETA 4!

Things are starting to get a little nuts with all these betas, but the addition of git and all that goes along with it is quite a big undertaking and the first couple of betas were pretty rough.  Things are definitely starting to smooth out, though.  This beta release focused mostly on bug fixes, but also contains another even bigger performance improvement for git status checking.  Here’s the list:

  • Added a button to the notification dialog to allow users to save the messages to a file
  • Fixed the “Initialize Repository” nautilus context menu to actually work
  • Fixed a bug where files would be modified but the status was not getting updated in nautilus or gedit
  • Added “Stage” and “Unstage” dialogs and context menu items.  These are similar to SVN’s Add dialog.  Basically, staging a file marks it as “added” and unstaging makes it “unversioned”.
  • Fixed some misc bugs in the repo browser and changes dialogs
  • Bug #395, In applypatch, if applying patch to a directory, don’t ask for the target directory
  • Fixed regression in commit window, all unversioned files should not be checked by default
  • Added the “Reset” context menu item to the log dialog
  • Implemented a mechanism for canceling git commands (so the cancel button actually does something)
  • The is_versioned method should use the local version of the status method, because it gets cached.  Quite good performance improvement for generating nautilus context menus
  • Made huge git status call performance improvements.  The linux kernel git repo used to take 229 secs for me, now takes ~5-6 secs.
  • Bug #384, In the branch dialog, convert the path to repository urls for both the to and from fields
  • Allow exporting from a git repository even if the given path is not a git repo (requires passing –vcs=git)
  • Bug #405, Format context menu labels to display underscores (for the ignore files list)
  • Bug #348, Allow the repo browser columns to be sortable
  • Bug #287, Add an emblem for unversioned files
  • If the gvfs-trash (delete) call fails, just permanently delete the file


Download RabbitVCS v0.14 beta3 at:

Note: We will have new packages in our PPA within a couple days.

Issue Tracker:

A big thanks and a great job to everyone on the team and everyone who
contributed to this release!


8 responses to “Release announcement for RabbitVCS BETA 4!”

  1. I noticed that sometimes Python starts using 100% CPU (after pushing/committing?) Can’t reproduce it yet…

  2. gpe says:

    I’ve made a deb package based on the 0.13 one but during the installation I’ve this error:

    /usr/lib/pymodules/python2.5/rabbitvcs/vcs/git/gittyup/ Warning: ‘as’ will become a reserved keyword in Python 2.6
    Compiling /usr/lib/pymodules/python2.5/rabbitvcs/vcs/git/gittyup/ …
    File “/usr/lib/pymodules/python2.5/rabbitvcs/vcs/git/gittyup/”, line 1071
    except Exception as e:
    SyntaxError: invalid syntax

    • Adam Plumb says:

      This is probably something you would want to put in our issue tracker.

      I didn’t realize the “Exception as” syntax only came about on 2.6. I’ll probably change it back to the comma-based syntax for now (i.e. “except Exception, e”)

  3. Hatem MASMOUDI says:

    Rabbit SVN dont offer any more the Update Menu to chekout a new SVN repository ?

  4. Xavier Garrido says:

    How to get ride of the unversionned emblem ? Btw it is also strange since some directories have an unversionned emblem and others have a ignored emblem ? How rabbitvcs deals with that ?

    The git support is a really cool feature. I’m testing it since one week and it works almost perfectly (sometimes Python is using 100% of CPU but I’m also playing with sparkleshare at the time being so …). Thanks a lot for your work.

  5. Anonymous says:

    Awesome work! I cannot wait for beta 5 (so I can checkout an svn). It is looking a lot better minus the svn check out problem.

  6. Rabbit SVN dont offer any more the Update Menu to chekout a new SVN repository ?