Ticket #2 (using Trac)

How should we handle Sentinel? Just as a branch?

No, a separate directory beside the one for FreakAuth in the root (like we already did actually, but this is just the answer).

Anytime that one of us will want to go in a way and not bothering others (see svn book), we'll discuss to decide anyway. But I just wanted to know if you had some ideas about that.

Well I think that at this point we should decide a common branching strategy in order to don't overwrite our changes if we are working on the same file simultaneulsy! ...I'm reading the docs and I'll suggest my viewpoint on this shortly...

We won't overwrite our changes, svn is here for that.

If someone worked on a file that you changed too, svn will ask you to update it in order to retrieve ones changes. Then there could be conflicts or not... (see this).

Branches are cool when a big change is wanted, but when it's not sure whether to keep it or not.

For example, I could do a branch to move countries in the lang file, so I can commit my work here (I'll need several commits, not very clear if I do it just in one). When I'm done, I can svn merge my changes to the trunk.

See the book (this link is better thatn the previous one):

Whenever someone needs to make a long-running change that is likely to disrupt the trunk, a standard procedure is to create a private branch and commit changes there until all the work is complete.