[PATCH] [continuous_builder] trivial improvements

The problem I see with trying to test this is that the patch doesn't actually change functionality -- it's just a code improvement. Well, the first change could perhaps be tested by running the tests on windows, but the second just looks like a straight-up code improvement.

Does anyone with a better knowledge of the patch triaging procedures wish to comment on what the procedure should be for this patch?

There are no possible test cases that I can think of to write for this patch, but it's a solid improvement in code quality as far as I'm concerned. +1

Tec, can you add a description to your patch so the rest of us knows what problem this patch solves?

After that we can discuss whether or not it needs tests.

C'mon Manfred, the patch is pretty obvious:

• use File.join instead of adding strings together, so that we're file-separator-independent;
• Use release_lock instead of deleting the lock file directly, to hide implementation from interface.

Replying to manfred:

Tec, can you add a description to your patch so the rest of us knows what problem this patch solves?

It doesn't really solve any problems - I wrote the patch because I thought the code could be written slightly better. IMO it's an improvement, but I appreciate that's very subjective, so don't really mind whether it's applied or not.

I don't want to start a whole discussion about this, but I think every ticket should at least have a short description. I'm willing to discuss this further on IRC>

Anyway, the code looks at lot better like this. +1 for applying.