Anyone using BRANCH.TODO?

[vila]

>>>>> John Arbash Meinel <john at arbash-meinel.com> writes:

    > This was originally intended as a way to put TODO information that
    > would be local to the feature branch they were working on.

I'm curious about how you guys and girls are doing that...

    > Such that by the time it was merged to trunk, it should be empty.

I don't use it, but I wish I could :)

I use various tricks to track what I want to achieve in a branch,
ranging from a TODO spelled differently or outside of the branch, to a
top thread in a loom or a COVER file where I gather the important points
I should mention when proposing for merge.

How about getting rid of BRANCH.TODO *and* adding it to .bzrignore ?
Hmm, not ideal either.

Just killing it has my vote anyway.

    > I don't know anyone using it, so I'm wondering if we should just
    > get rid of the file. TODO is also unused, but points people to our
    > bug tracker, etc. So if someone *did* just open TODO it at least
    > points them to something useful.

We may as well add a pointer to HACKING.txt and remove the link to the
blueprints.

        Vincent