As part of the on-going efforts to keep our software stable and secure, we put a lot of resources into testing it and finding holes that users should not encounter. This is important to us because we depend on our customers having positive experiences with RhodeCode Enterprise, and we also use our own tools daily so any mistakes hit us first.
Having moved from ClearCase to Mercurial last year, I have gone through the alteration to workflow that many users must get over on when switching from Subversion or CVS to Git or Mercurial. If you want to read a younger, fresh faced novice's take on the advantages of this, you can read this blog from 6 months ago Why Embrace Distributed Version Control Systems.
RhodeCode Enterprise 3 provides a central interface to Subversion, Mercurial and Git. Support for Subversion has been the biggest request from our customers. Almost all companies I’ve spoken to over the years want Subversion support to aid in migrating their developing environment to Git or Mercurial.
Pull requests form one half of the fork-pull workflow, but what is a pull request?
When you fork a repository, you normally carry out development work on the fork. When that work is finished, you request that it is pulled back into the repository. This request is known as a pull request.
We are happy to announce that RhodeCode Enterprise 3.2 is now available for general download. This release contains a whole chunk of new changes; improved functionality, security updates, bug fixes, and some styling. For the finer details you can read our release notes.