[Rivet] Move bootstrap into main repository for versioning?

[Andy Buckley]

On 06/02/14 11:58, David Grellscheid wrote:
> Hi Frank,
> 
>> The current revision (ef0f9730654d) is fine for 2.0.0. Let me know
>> once you have tagged it
> 
> Done, it's a named branch to allow...
> 
>> a bugfix on such a tag in case we notice something that is missing
> 
> So as usual we need to make sure we check in things on the right branch!
> The default branch can now lose all functionality needed for 2.0.0
> compatibility.
> 
> The download URL is
> 
>  http://rivet.hepforge.org/hg/bootstrap/raw-file/2.0.0/rivet-2-bootstrap
> 
>> Is there any benefit in having the bootstrap in a separate repo with
>> manual tagging instead of in the main Rivet repo and thus
>> automatically tagged?
> 
> Yes, I think it does not belong _inside_ Rivet. It's something external
> that needs bugfixes independently of the main Rivet tags.

I agree, we find bug fixes for the bootstrap script after the Rivet
release is made (and is 100% bug-free, hrmm). This way we can use the
tags for different reasons:

- in the Rivet repo the tag indicates what repo state corresponds to the
release with that number, and should generally be unchanged once made

- in the bootstrap repo the tag tells users how to download a script
which will build the Rivet version named in the tag. If the script is
found to be buggy for that release, we can bugfix it and move the tag to
the appropriate revision. (The named branch is a good idea.)

If everyone is happy, I will release the new Rivet and YODA this afternoon.

Andy

-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow / PH Dept, CERN