[Rivet] Move bootstrap into main repository for versioning?

[Frank Siegert]

Thanks, David.

The separation rivet<->bootstrap sounds reasonable, although I was a
bit worried about the hg "overhead" involved. But since I'm usually
not the one doing the releases I probably won't have to worry about
creating the release branches of the bootstrap script. I assume we
will create new bootstrap release branches for every Rivet release
even if the script didn't need any changes, right?

I have updated GettingStarted now, and at that time found it a bit
strange to have a 2.0.0/rivet-2-bootstrap script. Should we take this
opportunity to sort this into

2.0.0/rivet-bootstrap
2.0.0/rivet-bootstrap-lcg
1.9.0/rivet-bootstrap-lcg

?

If you agree, I'm happy to update the GettingStarted page, but it
would be best if you could do the hg re-organisation as I would
probably fail to move something from one branch to another without
messing it up.

Cheers,
Frank


On 6 February 2014 11:58, David Grellscheid
<david.grellscheid at durham.ac.uk> 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.
>
> See you,
>
>   David