<div dir="ltr">All things being equal, I'd prefer Richard Smith's proposal that doesn't involve needing a new/old numbering scheme, but lets us keep a single numbering/redirection (& I doubt we need the first 200 bugs in any case - has anyone referred to bugs that early in the last 5 years, say? But wouldn't mind if they were copied in with different numbers/some kind of redirection (but hey, if we can rewrite bug contents - we could always move the existing 200 bugs (but I guess some are pull requests and we can't totally rewrite those into bugs?) up into the new numbering range once the necessary numbers are reserved)).<br><br>But I understand the single numbering preserving option is likely more complicated/costly & thus not an equal candidate - just my minor preference.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 20, 2020 at 9:58 PM Tom Stellard 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">On 04/20/2020 04:08 PM, James Y Knight wrote:<br>
> 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:<br>
> 1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.<br>
> 2. The numbering can be fully-controlled.<br>
> Once the bugs are migrated to /some/ 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>
> <br>
<br>
This seems like a good approach to me.<br>
<br>
> We could also just have <a href="http://llvm.org/PR#%23%23" rel="noreferrer" target="_blank">llvm.org/PR###</a> <<a href="http://llvm.org/PR#%23%23" rel="noreferrer" target="_blank">http://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" rel="noreferrer" target="_blank">https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html</a>).<br>
> <br>
<br>
Would we even need a mapping file for this if we are able to get bugzilla id N<br>
to be archived to GitHub issue id N?<br>
<br>
-Tom<br>
<br>
> Then we could introduce a new naming scheme for github issue shortlinks.<br>
> <br>
> On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>> wrote:<br>
> <br>
> On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>> wrote:<br>
> <br>
> 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">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">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>
> <br>
> <br>
> 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" rel="noreferrer" target="_blank">llvm.org/PRxxxxx</a> <<a href="http://llvm.org/PRxxxxx" rel="noreferrer" target="_blank">http://llvm.org/PRxxxxx</a>>, and if we can preserve all the issue numbers this would ease the transition pain substantially.<br>
> <br>
> <br>
> 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">llvm-dev@lists.llvm.org</a> <mailto:<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>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<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>
<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>