[Rivet] Minor problems in Rivet 1.5.0

[Andy Buckley]

On 10/05/11 13:39, Frank Siegert wrote:
> Hi Andy,
>
> On 10/05/11 14:13, Andy Buckley wrote:
>> and I think we should then
>> pull the singleton into the trunk, where it *will* break things.
>
> I would prefer if this could go on a branch as long as we know that
> it'll break things (and won't be fixed within a day or so). There are
> quite a few people who are using Rivet trunk (partly because we have
> recommended this!) and might not be aware of the update freeze that they
> should adhere to. So by principle of least surprise I'd say let's leave
> trunk in a working state as far as we can.

I was trying to find a way to ensure that "developers" other than myself 
would have to confront this issue. My suspicion is that if it sits on a 
branch then only I will check it out, and all that will happen is that 
the truck changes get periodically merged onto the branch! Any 
suggestions? Yes, I know it's a problem in "my bit", and no, I don't 
really know how to fix it ;)

Andy

-- 
Dr Andy Buckley
SUPA Advanced Research Fellow
Particle Physics Experiment Group, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.