Releasing Software is not just packing latest version to tarball and send to SFTP server. It requires preparation and some planning to be done properly. I'll describe release procedure I applied on one of my latest projects. Supporting version control system is GIT. The aims for releasing procedure designed: allow for testing window before release… Continue reading Software Releases Using GIT
Let's say you tracked someone broke HEAD of trunk and you want to reverse that single commit from main branch. Subversion makes very handy syntax for reverse merges: svn merge -c -19203 https://REPO_URL In example above you do reverse merge of 19203 revision (note "-" sign before revision number). After that merge: Inspect if workspace… Continue reading Subversion: How To Revert Single Commit
You probably already know that Subversion stores some kind of metadata for all files added to repository. It's called "properties" in Subversion vocabulary. This key-value map is responsible for registering ingored files masks, file attributes, internal file content type etc. The property I'm going to present today is "mime-type". It describes file content in similar… Continue reading Why svn:mime-type does matter?
What's the purpose of internal project documentation? To help people do their jobs. Developers need the knowledge to be distributed across the team, testers need definition of proper system behaviour, marketing needs information on product features to sell it. Questions Important knowledge that may be required by developers doing updates may be summarized in few… Continue reading Do not reformat whole files on commit, PLEASE!
Aplikacja.info believes in continuous integration and frequent reases, so uses so-called stable trunk policy. That means: at any time any developer can make installation from trunk to production systems. How stable trunk can be achieved? any commit done to trunk is protected by set of automated tests that should run 100% clean (more critical project… Continue reading Peer code reviews with Subversion