github freebsd and svn freebsd

[Ed Maste]

On 6 September 2018 at 20:11, Warner Losh <imp at bsdimp.com> wrote:
>
>> Assuming we're confident the issue in the svn mirroring process is
>> fixed and will not recur we can redo the conversion, with a one-time
>> change to all hashes from the offending commit on, and they would not
>> change again in the future.
>
> What is the upgrade story for current users? How do they cut over? We need a
> how to or something in the handbook.

Yes, we'd need to have a fully documented migration process, and we
should be able to have both 'old' and 'new' branches exist in parallel
for some time.

One way we could handle the mechanics of the migration itself is:

* Create an alias for the current master branch - say, master-gen1
* Continue running the existing conversion
* Start running a fixed svn-git conversion which pushes to master-gen2
* Document the process for migrating downstream work from one to the other
* Switch master to master-gen2
* Deprecate master-gen1 after a suitable period

Because of the way git works the additional branch would result in
only a nominal increase in repository size.