Thanks for the draft! Comments inline: On Wed, Jan 17, 2018 at 10:31 PM, Alexandre Viau <av...@debian.org> wrote:
> On 17/01/18 08:05 AM, Michael Stapelberg wrote: > > I’d be happy to review any draft announcement you come up with. > > > > Alright. > > Here is a draft announcement: > > Dear pkg-go contributors, > > I will be migrating all of pkg-go's Alioth repositories to > salsa.debian.org on January 29. > > === About the migration === > > - A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org when > the migration starts and when it ends > > - All repositories in git.debian.org:/git/pkg-go/packages will be > migrated to the pkg-go-team group on salsa.debian.org[1] You should join > the group if you are not already in it! > > - Repositories will keep the same name, with ".git" removed. > > - HTTP anonscm.debian.org links of migrated repositories will be > redirected to the new location. > for example, you can test the following links: > - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing > - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git > > === During the migration === > > - Your pushes could be denied because the repository no longer exists. > Don't panic! It was moved to Gitlab. > > - You may start using salsa repositories immediately after they are > created. > > - If you push during the migration, take a moment to confirm that your > changes are available on salsa > > === After the migration === > > - On the next upload of your packages, please replace the VCS-* > anonscm.debian.org links with the proper salsa.debian.org links. > > For example: > https://anonscm.debian.org/cgit/pkg-go/packages/syncthing -> > https://salsa.debian.org/pkg-go-team/syncthing > https://anonscm.debian.org/git/pkg-go/packages/syncthing.git -> > https://salsa.debian.org/pkg-go-team/syncthing.git > > You might want to wait a couple of days after the migration before > spending time doing this because I might automate it for all repositories. > Let’s figure this out before starting the process :). I’m in favor for automating the step. The less people have to do mindless work that can easily go wrong, the better (as evidenced by a number of incorrect Vcs-* tags in our packages). > > - A copy of the migrated repositories will remain available in > “A read-only copy” please. > git.debian.org:/git/pkg-go/packages-migrated-to-salsa > > - You will still be able to create repositories on Alioth, but there > will be no other bulk migration. > > - If all went well, we might disable repository creation on Alioth a > couple of days after the migration. > I’d like to disable repository creation at the start of the migration. There’s no point in allowing backslide/stragglers like that. Everything should be in one place. > > - You may point your git working directories to the new remote address > with this oneliner: > ``git remote set-url origin g...@salsa.debian.org:pkg-go-team/$(git > config --get remote.origin.url | tr "/" "\n" | tail -n 1)`` > > 1. https://salsa.debian.org/pkg-go-team > > Cheers, > > -- > Alexandre Viau > av...@debian.org > > > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers