<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>+1 to James's take</p>
<p>I'd prefer simplicity of implementation over perfection here.</p>
<p>Philip<br>
</p>
<div class="moz-cite-prefix">On 4/20/20 4:08 PM, James Y Knight via
llvm-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAA2zVHpODRvXWz5CCcAKzgJM2Q=FgEWbctoPw34on75C1Pn0zQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">In a previous discussion, one other suggestion had
been to migrate all the bugzilla bugs to a
separate initially-private "bug archive" repository in github.
This has a few benefits:
<div>1. If the migration is messed up, the repo can be deleted,
and the process run again, until we get a result we like.</div>
<div>2. The numbering can be fully-controlled.</div>
<div>Once the bugs are migrated to <i>some</i> github
repository, individual issues can then be "moved" between
repositories, and github will redirect from the
movefrom-repository's bug to the target repository's bug.<br>
</div>
<div><br>
</div>
<div>We could also just have <a href="http://llvm.org/PR###"
moz-do-not-send="true">llvm.org/PR###</a> be the url only
for legacy bugzilla issue numbers -- and have it use a file
listing the mappings of bugzilla id -> github id to
generate the redirects. (GCC just did this recently for svn
revision number redirections, <a
href="https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html"
moz-do-not-send="true">https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html</a>).</div>
<div><br>
</div>
<div>Then we could introduce a new naming scheme for github
issue shortlinks.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Apr 20, 2020 at 3:50
PM Richard Smith via llvm-dev <<a
href="mailto:llvm-dev@lists.llvm.org" moz-do-not-send="true">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 dir="ltr">
<div dir="ltr">On Mon, 20 Apr 2020 at 12:31, Tom Stellard
via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I wanted to continue discussing the plan to migrate from
Bugzilla to Github.<br>
It was suggested that I start a new thread and give a
summary of the proposal<br>
and what has changed since it was originally proposed in
October.<br>
<br>
== Here is the original proposal:<br>
<br>
<a
href="http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html</a><br>
<br>
== What has changed:<br>
<br>
* You will be able to subscribe to notifications for a
specific issue<br>
labels. We have a proof of concept notification
system using github actions<br>
that will be used for this.<br>
<br>
* Emails will be sent to llvm-bugs when issues are
opened or closed.<br>
<br>
* We have the initial list of labels: <a
href="https://github.com/llvm/llvm-project/labels"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/llvm/llvm-project/labels</a><br>
<br>
== Remaining issue:<br>
<br>
* There is one remaining issue that I don't feel we have
consensus on,<br>
and that is what to do with bugs in the existing
bugzilla. Here are some options<br>
that we have discussed:<br>
<br>
1. Switch to GitHub issues for new bugs only. Bugs
filed in bugzilla that are<br>
still active will be updated there until they are
closed. This means that over<br>
time the number of active bugs in bugzilla will slowly
decrease as bugs are closed<br>
out. Then at some point in the future, all of the bugs
from bugzilla will be archived<br>
into their own GitHub repository that is separate from
the llvm-project repo.<br>
<br>
2. Same as 1, but also create a migration script that
would allow anyone to<br>
manually migrate an active bug from bugzilla to a GitHub
issue in the llvm-project<br>
repo. The intention with this script is that it would
be used to migrate high-traffic<br>
or important bugs from bugzilla to GitHub to help
increase the visibility of the bug.<br>
This would not be used for mass migration of all the
bugs.<br>
<br>
3. Do a mass bug migration from bugzilla to GitHub and
enable GitHub issues at the same time.<br>
Closed or inactive bugs would be archived into their own
GitHub repository, and active bugs<br>
would be migrated to the llvm-project repo.<br>
</blockquote>
<div><br>
</div>
<div>Can we preserve the existing bug numbers if we
migrate this way? There are lots of references to
"PRxxxxx" in checked in LLVM artifacts and elsewhere in
the world, as well as links to <a
href="http://llvm.org/PRxxxxx" target="_blank"
moz-do-not-send="true">llvm.org/PRxxxxx</a>, and if we
can preserve all the issue numbers this would ease the
transition pain substantially.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
The key difference between proposal 1,2 and 3, is when
bugs will be archived from bugzilla<br>
to GitHub. Delaying the archiving of bugs (proposals 1
and 2) means that we can migrate<br>
to GitHub issues sooner (within 1-2 weeks), whereas
trying to archive bugs during the<br>
transition (proposal 3) will delay the transition for a
while (likely several months)<br>
while we evaluate the various solutions for moving bugs
from bugzilla to GitHub.<br>
<br>
<br>
The original proposal was to do 1 or 2, however there
were some concerns raised on the list<br>
that having 2 different places to search for bugs for
some period of time would<br>
be very inconvenient. So, I would like to restart this
discussion and hopefully we can<br>
come to some kind of conclusion about the best way
forward.<br>
<br>
Thanks,<br>
Tom<br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</body>
</html>