<div dir="ltr">I was about to suggest the same thing as Mara (email came in just as I was about to hit send 🙂). It should be pretty easy to do this:<div><br></div><div>1) For each bugzilla bug number, create a GitHub issue with a name like "placeholder for bugzilla migration" and a link to the corresponding bugzilla bug (and maybe some explanation of what's going on so it's less weird to people coming across it)</div><div>2) To avoid these issues clogging up the GitHub, close them all to start with (they can be reopened later if they correspond to an open issue on bugzilla)</div><div>3) Stop new issue creation on Bugzilla</div><div>4) Add GitHub issues in the same way as (1) for any new Bugzilla bugs that were filed between (1) and (3). Technically you could start by stopping new issue creation on Bugzilla, but it's probably nice to minimize the window where there's no way to file issues.</div><div>5. Open up the GitHub for new issue creation</div><div>6. Figure out how to migrate all the Bugzilla bugs without time pressure</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 12, 2021 at 11:48 AM Mara Sophie Grosch via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>Maybe we can close bugzilla bug creation, create placeholder issues for the existing bugzilla bugs, create new bugs on GitHub and fill those placeholders asynchronously?<br><br>Best, Mara<br><br><div class="gmail_quote">Am 12. November 2021 19:45:11 UTC schrieb Philip Reames via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<p><br>
</p>
<div>On 11/12/21 11:36 AM, Mehdi AMINI
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Nov 12, 2021 at
11:15 AM Philip Reames via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I've
raised this point once before, but I think it's time to
raise it again.<br>
<br>
I believe we should drop the goal of keeping bug numbers in
sync between <br>
github and the legacy llvm bug database. We do need a
one-to-one <br>
mapping, but the numbers can be distinct. This requires a
bit of extra ugliness in terms of needing to add a comment
to every bug (both copies) <br>
with a link to the other, but this is a minimal badness, and
stops <br>
mattering fairly quickly after the transition<br>
</blockquote>
<div><br>
</div>
<div>It is even better than this: if we can generate a map of
old IDs to new IDs when doing the conversion, it really
isn't difficult to keep the existing URL working
(redirecting to the right migrated GitHub issue).</div>
<div><br>
I may be missing something about other advantages of mapping
1-1?<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Continuing to hold back the transition of new bugs to github
is causing <br>
real immediate harm. I strongly believe we are better off
moving now <br>
with an imperfect system than waiting any longer.<br>
</blockquote>
<div><br>
</div>
<div>Is the ID mapping really the only issue keeping us back
though?</div>
</div>
</div>
</blockquote>
It seems to be a major one. If nothing else, without it we could
migrate a subset of bugs which happen to migrate cleanly, and then
come back and handle the ones with issues at a arbitrarily later
point. Or we could simply close creation of *new* bugzilla bugs,
and start all new traffic on github without waiting for a migration
at all. The whole reason we're not doing that (seems to be) is that
we want to preserve the low bug numbers for 1-to-1 correspondence
purposes. <br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div> </div>
<div>-- </div>
<div>Mehdi</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Philip<br>
<br>
On 11/1/21 9:13 AM, Anton Korobeynikov via llvm-dev wrote:<br>
> Dear All,<br>
><br>
> Over the weekend we tried to perform a "dry-run"
migration –<br>
> conversion of all 51k+ bugzilla issues to a temporary
GitHub project.<br>
><br>
> Unfortunately, the migration failed due to some obscure
error at the<br>
> GitHub side. So far, GitHub is unable to tell us what
the problem is,<br>
> how to solve / workaround it and how to proceed with
the migration<br>
> (not to say, how to prevent similar issues during the
real migration).<br>
> So far this is the real show-stopper.<br>
><br>
> We will continue pushing, however, I do not have any
ETA on when we<br>
> will be able to continue with the bugzilla migration.<br>
><br>
> I'm sorry to disappoint you, but sometimes things are
beyond my control.<br>
><br>
><br>
><br>
> On Fri, Oct 29, 2021 at 1:23 AM Anton Korobeynikov<br>
> <<a href="mailto:anton@korobeynikov.info" target="_blank">anton@korobeynikov.info</a>>
wrote:<br>
>> Dear Fellow LLVMers,<br>
>><br>
>> I believe we were able to work-around the majority
of GitHub<br>
>> deficiencies (at least those that were
show-stoppers). We are checking<br>
>> the results. Hopefully I will be able to return to
you with the final<br>
>> migration roadmap soon.<br>
>><br>
>> Stay tuned!<br>
>><br>
>> --<br>
>> On behalf of the LLVM Foundation,<br>
>> Anton Korobeynikov<br>
><br>
><br>
> --<br>
> With best regards, Anton Korobeynikov<br>
> Department of Statistical Modelling, Saint Petersburg
State University<br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
</blockquote>
</blockquote></div><div style="white-space:pre-wrap"><div>-- <br>Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</div></div></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>