On Mon, Oct 04, 2010 at 10:55:02PM +0200, Laurens Van Houtven wrote:
> Hello,
> 
> 
> I'm trying to migrate a Trac workflow to Fossil. Here's what it looks like:
> 
> For each feature:
> 1. create ticket
> 2. create branch
> 3. implement
> 4. submit branch for review
> 5. review: if not good, back to 3
> 6. merge branch to trunk
> (trunk gets handed off to continuous integration/deployment system)
> 
> It feels kind of unwieldy. I'm trying to figure out if that's because
> I'm not used to Fossil, or because I'm trying to make a cat bark. Is
> Fossil not built to work this way? It could be a misunderstanding, but
> I saw something about Fossil's autosync feature being all about
> preventing lots of "needless" branching. What is workflow supposed to
> look like instead?
You can review against the trunk version it was updated from. As any DVCS,
fossil does not provide methods to guarantee that noone commited over the same
parent as you, so if that happens, you then will have to merge two heads of a
single branch. This is inherent in DVCS, and not related to your review process.

> Is there a decent way of filtering tickets on the ones which are up
> for review and which ones aren't? In trac, I did this with tags; but
> fossil doesn't appear to have tags for tickets.
You can write your own queries for fossil, and your own fields in each ticket.
In the web Admin -> Ticket configuration you can find that.

> Also what do you people use for code review? I can imagine using
> fossil diff for this, I guess. Ideas welcome.
I still have not moved our scripts from svn to fossil, but what we used to do
was prepare two checkout directories, one with the last trunk version merged in,
and the other with the branch to review. Then we used meld (meld.sf.net) to get
a diff while being able to edit the files.
Then we leave comments and commit in the branch with the review results.

I wonder how difficult it will be in fossil to find "the version of the parent
branch last merged into a child branch".

Regards,
Lluís.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to