For the uninitiated, Duality SVN is a Subversion (SVN) frontend written in Python and PyQt for the SVN commandline tools. One of its goals is to provide a UI streamlined for optimal service of daily client-side version control workflows, making it easier and faster to concentrate on your core activites instead, be it developing code, writing documentation, or working on art projects.
The other (and original founding goal) was to provide a branch management workflow non-reliant on SVN's slow and fickle "merge" tools, which were a significant barrier to successful branch management for many users.
Features provided by Duality SVN in the current release:
- Streamlined GUI and hotkey access for daily development/version-control work - Update, Commit, Add/Delete, Revert, Mark Conflicts as Resolved
- "Status list" with coloured status indicators and ability to selectively operate on chosen files only
- Versioned files can be locally ignored (i.e. not shown in status reports or for commits) as "local modifications"
- Commit log editor with ability to load and save commit logs from user-specified files, as well as functional word-wrapping facilities
- Prior to committing, any files with invalid statuses have these issues automatically rectified
- Checkout sources from repository and set up new project for these
- Create new project for existing checkouts
- Branching support - The creation of new branches is not yet complete in this initial release and hasn't been tested yet, but may be somewhat functional at this stage already. Use with caution.
- This was originally earmarked as a launch-day feature, although this will now be completed in a future release (hopefully not too far away).
- Viewing change logs
- Nice coloured display of diffs
- Creating Patches
- Apply Patches - This is somewhat complicated, and may require the inclusion of foreign components (or yet another homebrew solution!). We'll see...
So, without further ado, some links!
Install Instructions: http://code.google.com/p/dualitysvn/wiki/Install_SysReqs
This is the first time I've managed a full software release cycle myself, so apologies in advance if there are hiccups.