I started a document describing the changes we agreed on, the rationale behind them, the old/new workflows and the migration strategy.
Quote from the commit message (https://anonscm.debian.org/git/pkg-go/website.git/commit/?id=866810cfeea8086dbdfc0176b148f7a063e3ac0b): > Quite a number of points haven’t been entirely researched yet. > > Any help is welcome. > > We can do mass-migrations of packages once the document is in a good shape and > the steps have been tested on a few packages. Find the HTML version at https://pkg-go.alioth.debian.org/workflow-changes.html I hope I can make some progress on this in the next few days. Any help is welcome. On Mon, Nov 6, 2017 at 7:15 PM, Martín Ferrari <tin...@tincho.org> wrote: > On 06/11/17 15:04, Martín Ferrari wrote: > >> I have added something that I think it is widely accepted, but was not >> explicitly discussed, and that I would like to be set on policy: should >> we mandate merging of upstream code in debian branch? > > Just to clarify: I don't think this new point should delay the rest of > the decisions. I think the other points had enough time by now to be > considered settled. > > > -- > Martín Ferrari (Tincho) -- Best regards, Michael _______________________________________________ Pkg-go-maintainers mailing list Pkgemail@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers