> We are in the early stages of git migration. Hopefully you won't be dropping support for Mercurial before we migrate.
We'll definitely keep supporting Mercurial in `taskcluster/taskgraph` until the last fxci repo is migrated off of Mercurial. And I think we can support it for a "reasonable" amount of time in `gecko_taskgraph` as well (I don't know what reasonable is yet). But if we ever get to a point where Gecko is fully off of Mercurial but comm isn't and there's no end in sight, then at that point hard forking Mercurial only stuff into comm taskgraph feels like it'll be the way to go. Because by then it would be truly comm specific.
Bug 1986773 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> We are in the early stages of git migration. Hopefully you won't be dropping support for Mercurial before we migrate.
We'll definitely keep supporting Mercurial in `taskcluster/taskgraph` until the last fxci repo is migrated off of Mercurial. And I think we can support it for a "reasonable" amount of time in `gecko_taskgraph` as well (I don't know what reasonable is yet). But if we ever get to a point where Gecko is fully off of Mercurial but comm isn't and there's no end in sight, then at that point hard forking Mercurial only stuff into comm taskgraph feels like it'll be the way to go.