PUBLIC MARKS from nhoizey with tags dev & svn

Malgré l'annonce faite le 1er avril, c'est bel et bien possible, et le support des commit arrive aussi, incroyable.

"Handy PHP5 tool which mirrors two SVN repositories by reproducing each and every commit

"the whole svn:externals thing seems a bit like a hack, or at least not a first class citizen in SVN land"

If we have several agile development teams working on the same codebase, how do we minimize the risk of stumbling over each other? How do we ensure that there always is a clean, releasable version at the end of each iteration?

Welcome to code.flickr Your one-stop shop for information, gossip and discussion with the Flickr developer community

Most software version control systems provide mechanisms for branching into multiple lines of development and merging source code from one development line into another. However, the techniques, policies and guidelines for using these mechanisms are often misapplied or not fully understood. This is unfortunate, since the use or misuse of branching and merging can make or break a parallel software development project. Streamed Lines is a pattern language for organizing related lines of development into appropriately diverging and converging streams of source code changes.

Starting with Subversion 1.3.1, our packages will be built containing Universal Binaries with native support for both PowerPC and Intel Macs

Continuous Integration, Source Control, a Wiki and a Bug-Tracker are all cornerstones of a functioning Agile development project.

As CVS is quite dated and Subversion (SVN) introduced some handy features (atomic transactions, Apache piggybacking, more convenient branching/tagging, tons of other improvements), we chose to go with SVN. The big question was: how to use it correctly?