At RhodeCode, we’ve built the world’s most secure version control system for enterprises and I am the creator of the RhodeCode project. As co-founder of the company RhodeCode I helped to make the project available and ready for production deployments in enterprises. All that started in 2010 as I first came up with the idea for RhodeCode
… and how it could had been avoided.
You likely have noticed the potential for security breaches around. There are threats from hackers, spies, corporate raiders, terrorists, professional criminals, and vandals – all leading to damages to the enterprise infrastructure and sometimes even the business itself. But one key aspect of security often missing from the discussion is protection of the source code. Not only is this aspect overlooked, it has amazing potential to cause serious harm in a multitude of obvious and not so obvious ways.
Today we release the minor upgrade 3.1.1 which fixes a potential security vulnerability of a 3rd party library. We recommend all users to upgrade to RhodeCode Enterprise 3.1.1 as soon as possible.
As startup founders, Marcin and I have noticed that proverbial “pat on the back” often seems elusive and not within the job scope. Rarely do we get a pure, elevated, long lasting sense of accomplishment like we did last week when my team announced the biggest release in our history: the release of RhodeCode Enterprise 3.
One discussion that often raises its head in developer circles is workflow. How you do is often as important as what you do, especially when you are the one doing it!