llvm dev - Nov 2021 - Update on Bugzilla migration

Dear All,

Over the weekend we tried to perform a "dry-run" migration –
conversion of all 51k+ bugzilla issues to a temporary GitHub project.

Unfortunately, the migration failed due to some obscure error at the
GitHub side. So far, GitHub is unable to tell us what the problem is,
how to solve / workaround it and how to proceed with the migration
(not to say, how to prevent similar issues during the real migration).
So far this is the real show-stopper.

We will continue pushing, however, I do not have any ETA on when we
will be able to continue with the bugzilla migration.

I'm sorry to disappoint you, but sometimes things are beyond my control.



On Fri, Oct 29, 2021 at 1:23 AM Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>
> Dear Fellow LLVMers,
>
> I believe we were able to work-around the majority of GitHub
> deficiencies (at least those that were show-stoppers). We are checking
> the results. Hopefully I will be able to return to you with the final
> migration roadmap soon.
>
> Stay tuned!
>
> --
> On behalf of the LLVM Foundation,
> Anton Korobeynikov


--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University

On Mon, Nov 1, 2021 at 9:14 AM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Dear All,
>
> Over the weekend we tried to perform a "dry-run" migration –
> conversion of all 51k+ bugzilla issues to a temporary GitHub project.
>
> Unfortunately, the migration failed due to some obscure error at the
> GitHub side. So far, GitHub is unable to tell us what the problem is,
> how to solve / workaround it and how to proceed with the migration
> (not to say, how to prevent similar issues during the real migration).
> So far this is the real show-stopper.
>
> We will continue pushing, however, I do not have any ETA on when we
> will be able to continue with the bugzilla migration.
>
> I'm sorry to disappoint you, but sometimes things are beyond my
control.
>
Could you give a rough summary/details on the interactions with GitHub? Are
they responsive? Expecting to provide more detail in some sort of timeline
(not a guarantee, but more than a "We don't know, and we don't have
any
particular plans/expectation that we'll ever know, what's wrong
here")?

>
>
>
> On Fri, Oct 29, 2021 at 1:23 AM Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
> >
> > Dear Fellow LLVMers,
> >
> > I believe we were able to work-around the majority of GitHub
> > deficiencies (at least those that were show-stoppers). We are checking
> > the results. Hopefully I will be able to return to you with the final
> > migration roadmap soon.
> >
> > Stay tuned!
> >
> > --
> > On behalf of the LLVM Foundation,
> > Anton Korobeynikov
>
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211101/77c0d047/attachment.html>

I've raised this point once before, but I think it's time to raise it
again.

I believe we should drop the goal of keeping bug numbers in sync between 
github and the legacy llvm bug database.  We do need a one-to-one 
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) 
with a link to the other, but this is a minimal badness, and stops 
mattering fairly quickly after the transition

Continuing to hold back the transition of new bugs to github is causing 
real immediate harm.  I strongly believe we are better off moving now 
with an imperfect system than waiting any longer.

Philip

On 11/1/21 9:13 AM, Anton Korobeynikov via llvm-dev
wrote:
> Dear All,
>
> Over the weekend we tried to perform a "dry-run" migration –
> conversion of all 51k+ bugzilla issues to a temporary GitHub project.
>
> Unfortunately, the migration failed due to some obscure error at the
> GitHub side. So far, GitHub is unable to tell us what the problem is,
> how to solve / workaround it and how to proceed with the migration
> (not to say, how to prevent similar issues during the real migration).
> So far this is the real show-stopper.
>
> We will continue pushing, however, I do not have any ETA on when we
> will be able to continue with the bugzilla migration.
>
> I'm sorry to disappoint you, but sometimes things are beyond my
control.
>
>
>
> On Fri, Oct 29, 2021 at 1:23 AM Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
>> Dear Fellow LLVMers,
>>
>> I believe we were able to work-around the majority of GitHub
>> deficiencies (at least those that were show-stoppers). We are checking
>> the results. Hopefully I will be able to return to you with the final
>> migration roadmap soon.
>>
>> Stay tuned!
>>
>> --
>> On behalf of the LLVM Foundation,
>> Anton Korobeynikov
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Anton,
>Over the weekend we tried to perform a "dry-run" migration –
>conversion of all 51k+ bugzilla issues to a temporary GitHub project.
Do we  feel there could be value in sharing access to this temporary GitHub
project with a wider audience so we can see how the issues would look? This
might raise interest and excitement but also might help to ensure we don't
land something that people find hard to work with.

For example, I'm only interested in a very specific subset of the
"bugs"
(clang-format), how easy will that be for me to see just those. Are
separate areas just labels? can we filter down to see just the areas we
want?

I'd personally like to see how easy its going to be to find those I want
and to see "what is new" in that area and "what I might work on
next"

For me I'd like people to specifically log bugs against
"clang-format" and
not  the old "Formatter" that it was in bugzilla so I'm interested
to
understand how in the future it might look and if there is any opportunity
to "clean" the data as we migrate.

For example do we plan on taking "[clang-format] [clang-tidy] type labels
from the subject lines and convert them into labels or projects?"

[image: image.png]

Just my 2p worth.

MyDeveloperDay.

On Mon, Nov 1, 2021 at 4:13 PM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Dear All,
>
> Over the weekend we tried to perform a "dry-run" migration –
> conversion of all 51k+ bugzilla issues to a temporary GitHub project.
>
> Unfortunately, the migration failed due to some obscure error at the
> GitHub side. So far, GitHub is unable to tell us what the problem is,
> how to solve / workaround it and how to proceed with the migration
> (not to say, how to prevent similar issues during the real migration).
> So far this is the real show-stopper.
>
> We will continue pushing, however, I do not have any ETA on when we
> will be able to continue with the bugzilla migration.
>
> I'm sorry to disappoint you, but sometimes things are beyond my
control.
>
>
>
> On Fri, Oct 29, 2021 at 1:23 AM Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
> >
> > Dear Fellow LLVMers,
> >
> > I believe we were able to work-around the majority of GitHub
> > deficiencies (at least those that were show-stoppers). We are checking
> > the results. Hopefully I will be able to return to you with the final
> > migration roadmap soon.
> >
> > Stay tuned!
> >
> > --
> > On behalf of the LLVM Foundation,
> > Anton Korobeynikov
>
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211113/f756a759/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 16050 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211113/f756a759/attachment-0001.png>