Andrew Lee <[email protected]> writes: > They offered a very good strategy to help us accelerate our progress > for the Forky release cycle: > 1. Upload new tooling to `unstable`
+1 -- I think delaying the unstable upload will delay the entire effort. > 2. Please suggest a new package name for new tooling: dh-go? > 3. Deprecate legacy `dh-golang`: > We may file an `important` severity bug against the legacy > `dh-golang` package after the new tooling available in unstable. This > is to announce the deprecation, and may upgrade to RC later when new > tooling is more ready while we are approaching to the Forky freeze in > the next release cycle. > > 4. Provide a transition package to enfore the transition when it's ready: > Once we have more confidence on the new tooling, we can then provide > a dummy/transition package to enforce the final migration from > `dh-golang` to `new tooling` acrossing the archive. Yes - a transition package once we've converted the problematic packages seems like a good idea. We won't ever be able to finish re-uploading all golang-* packages in Debian before forky. Thanks for working on this! /Simon
signature.asc
Description: PGP signature
