RFC: Switching from Bugzilla to Github Issues [UPDATED]

classic Classic list List threaded Threaded
50 messages Options
123
Reply | Threaded
Open this post in threaded view
|

RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.


The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.

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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
 
The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On 04/20/2020 12:49 PM, Richard Smith wrote:

> On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     Hi,
>
>     I wanted to continue discussing the plan to migrate from Bugzilla to Github.
>     It was suggested that I start a new thread and give a summary of the proposal
>     and what has changed since it was originally proposed in October.
>
>     == Here is the original proposal:
>
>     http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
>
>     == What has changed:
>
>     * You will be able to subscribe to notifications for a specific issue
>       labels.  We have a proof of concept notification system using github actions
>       that will be used for this.
>
>     * Emails will be sent to llvm-bugs when issues are opened or closed.
>
>     * We have the initial list of labels: https://github.com/llvm/llvm-project/labels
>
>     == Remaining issue:
>
>     * There is one remaining issue that I don't feel we have consensus on,
>     and that is what to do with bugs in the existing bugzilla.  Here are some options
>     that we have discussed:
>
>     1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
>     still active will be updated there until they are closed.  This means that over
>     time the number of active bugs in bugzilla will slowly decrease as bugs are closed
>     out.  Then at some point in the future, all of the bugs from bugzilla will be archived
>     into their own GitHub repository that is separate from the llvm-project repo.
>
>     2. Same as 1, but also create a migration script that would allow anyone to
>     manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
>     repo.  The intention with this script is that it would be used to migrate high-traffic
>     or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
>     This would not be used for mass migration of all the bugs.
>
>     3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
>     Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
>     would be migrated to the llvm-project repo.
>
>
> 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 llvm.org/PRxxxxx <http://llvm.org/PRxxxxx>, and if we can preserve all the issue numbers this would ease the transition pain substantially.
>  

For all 3 proposals we want to be able to preserver the llvm.org/PRxxxx links so that
they continue to provide useful information.  Eventually once bugzilla is shut down,
those links would point to an issue somewhere in GitHub.

We don't have a solution for this today and this is one of the reasons why proposal
3 will take so long to implement, because we need to solve this problem before we start any
kind of transition.

This is also the reason why proposals 1 and 2 were originally favored, because they allow us
to transition to GitHub issues for new bugs sooner, while still maintaining the PRxxxx
links in bugzilla.  This gives us time to work out a good long-term solution to maintaining
the links without further delaying the transition to GitHub issues.

-Tom



>
>     The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
>     to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
>     to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
>     transition (proposal 3) will delay the transition for a while (likely several months)
>     while we evaluate the various solutions for moving bugs from bugzilla to GitHub.
>
>
>     The original proposal was to do 1 or 2, however there were some concerns raised on the list
>     that having 2 different places to search for bugs for some period of time would
>     be very inconvenient.  So, I would like to restart this discussion and hopefully we can
>     come to some kind of conclusion about the best way forward.
>
>     Thanks,
>     Tom
>
>     _______________________________________________
>     LLVM Developers mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
> 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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
Well... I hate to say this, but quite unlikely. Unfortunately, there
were significant changes in GitHub opensource team and these days they
are much less responsive than they used to be during our github
migration. I asked this question several times, and unfortunately,
there is no answer. I will certainly keep trying.

The problem here is there is no way to assign / control issue numbers
at all. They are just automatically assigned in sequential order.
While it might be possible to utilize this while migrating everything
to, say, a special archive project on GitHub, we will not be able to
control the numbers assigned should we migrate the issues one-by-one
or just move from archive to main project.

So, the only viable way seems to be plain big mapping from bugzilla to
github issue numbers without anything simple like "llvm.org/PRxxxxxx
becomes https://github.com/llvm/llvm-project/issues/xxxxxx".


--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
Just to clarify a bit: what I wanted to say is that it's unlikely
that we will be able to ensure that bugzilla issue numbers after
migration would coincide with github issue numbers. And therefore
proper mapping will be necessary. And this mapping would be more
complex than just rewriting the URL.


On Mon, Apr 20, 2020 at 11:25 PM Anton Korobeynikov
<[hidden email]> wrote:

>
> > 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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
> Well... I hate to say this, but quite unlikely. Unfortunately, there
> were significant changes in GitHub opensource team and these days they
> are much less responsive than they used to be during our github
> migration. I asked this question several times, and unfortunately,
> there is no answer. I will certainly keep trying.
>
> The problem here is there is no way to assign / control issue numbers
> at all. They are just automatically assigned in sequential order.
> While it might be possible to utilize this while migrating everything
> to, say, a special archive project on GitHub, we will not be able to
> control the numbers assigned should we migrate the issues one-by-one
> or just move from archive to main project.
>
> So, the only viable way seems to be plain big mapping from bugzilla to
> github issue numbers without anything simple like "llvm.org/PRxxxxxx
> becomes https://github.com/llvm/llvm-project/issues/xxxxxx".
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
210 issues have been filed on github so far. That's negligible compared to the total number we have, so a minor additional effort for those seems acceptable if we can't actually clean them out and reuse the numbers.

So suppose we start with bugzilla issue #211 and migrate the issues to github one at a time, in order. That would preserve the existing bug numbering and all existing bugs, other than those first 210. For those 210, I'd suggest we file new issues on github, and add comments to github issue 1-210 indicating they've been migrated and the new issue number. (I'd be inclined to delete as much contents from those issues as possible and retain only the redirect to the new number.)

Would that work?

On Mon, 20 Apr 2020 at 13:33, Anton Korobeynikov via cfe-dev <[hidden email]> wrote:
Just to clarify a bit: what I wanted to say is that it's unlikely
that we will be able to ensure that bugzilla issue numbers after
migration would coincide with github issue numbers. And therefore
proper mapping will be necessary. And this mapping would be more
complex than just rewriting the URL.


On Mon, Apr 20, 2020 at 11:25 PM Anton Korobeynikov
<[hidden email]> wrote:
>
> > 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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
> Well... I hate to say this, but quite unlikely. Unfortunately, there
> were significant changes in GitHub opensource team and these days they
> are much less responsive than they used to be during our github
> migration. I asked this question several times, and unfortunately,
> there is no answer. I will certainly keep trying.
>
> The problem here is there is no way to assign / control issue numbers
> at all. They are just automatically assigned in sequential order.
> While it might be possible to utilize this while migrating everything
> to, say, a special archive project on GitHub, we will not be able to
> control the numbers assigned should we migrate the issues one-by-one
> or just move from archive to main project.
>
> So, the only viable way seems to be plain big mapping from bugzilla to
> github issue numbers without anything simple like "llvm.org/PRxxxxxx
> becomes https://github.com/llvm/llvm-project/issues/xxxxxx".
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On Mon, Apr 20, 2020 at 4:40 PM Richard Smith via cfe-dev <[hidden email]> wrote:
210 issues have been filed on github so far. That's negligible compared to the total number we have, so a minor additional effort for those seems acceptable if we can't actually clean them out and reuse the numbers.

So suppose we start with bugzilla issue #211 and migrate the issues to github one at a time, in order. That would preserve the existing bug numbering and all existing bugs, other than those first 210. For those 210, I'd suggest we file new issues on github, and add comments to github issue 1-210 indicating they've been migrated and the new issue number. (I'd be inclined to delete as much contents from those issues as possible and retain only the redirect to the new number.)

Would that work?
If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running...
Also, I'm not sure that all of the issues in Bugzilla are filed against things in the monorepo.
 

On Mon, 20 Apr 2020 at 13:33, Anton Korobeynikov via cfe-dev <[hidden email]> wrote:
Just to clarify a bit: what I wanted to say is that it's unlikely
that we will be able to ensure that bugzilla issue numbers after
migration would coincide with github issue numbers. And therefore
proper mapping will be necessary. And this mapping would be more
complex than just rewriting the URL.


On Mon, Apr 20, 2020 at 11:25 PM Anton Korobeynikov
<[hidden email]> wrote:
>
> > 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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
> Well... I hate to say this, but quite unlikely. Unfortunately, there
> were significant changes in GitHub opensource team and these days they
> are much less responsive than they used to be during our github
> migration. I asked this question several times, and unfortunately,
> there is no answer. I will certainly keep trying.
>
> The problem here is there is no way to assign / control issue numbers
> at all. They are just automatically assigned in sequential order.
> While it might be possible to utilize this while migrating everything
> to, say, a special archive project on GitHub, we will not be able to
> control the numbers assigned should we migrate the issues one-by-one
> or just move from archive to main project.
>
> So, the only viable way seems to be plain big mapping from bugzilla to
> github issue numbers without anything simple like "llvm.org/PRxxxxxx
> becomes https://github.com/llvm/llvm-project/issues/xxxxxx".
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
> If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running...
And pull requests (the numbering is common for issues and pull
requests) as well. And we cannot disable pull requests at all. And I'm
afraid the issues will need to be opened as well during the migration.
And now the real problem: should an "extra" pull request or issue
intervene in the migration there is no way to "reset" the counter
besides deleting the project and creating it once again. We could only
sacrifice some bugzilla issues to restore the numbering...


--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev <[hidden email]> wrote:
> If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running...
And pull requests (the numbering is common for issues and pull
requests) as well. And we cannot disable pull requests at all. And I'm
afraid the issues will need to be opened as well during the migration.
And now the real problem: should an "extra" pull request or issue
intervene in the migration there is no way to "reset" the counter
besides deleting the project and creating it once again. We could only
sacrifice some bugzilla issues to restore the numbering...

We can edit summaries and comments, presumably by API calls as well as by the web UI. So how about this:

Step 1: Preallocate sufficient github issue numbers. Make a bot account and with it file empty placeholder issues until we have N issues total, where N is the number of bugzilla bugs.
Step 2: Shut down the ability to file new bugzilla bugs, double-check we have enough placeholder bugs, then open up github for new issue submissions. Change llvm.org/PRxxxxx to redirect to github for xxxxx's higher than the transition point.
Step 3a: For each issue filed by the bot account, sync that bug's contents to the bugzilla entry: copy across the subject, all the comments, tags, and so on.
Step 3b: For each issue not filed by the bot account whose number is that of a bugzilla entry, file a new github bug and sync it with the bugzilla bug then add a tracking comment to the github bug saying what the new number is.

All we would need to do before we switch systems is steps 1 and 2. The data import can be done incrementally with no time constraints. Once transition is complete, we can change llvm.org/PRxxxxx (and existing bugzilla links, since I'm sure they exist in the wild too) to redirect to github, and shut down our bugzilla instance.

If new PRs are filed during step 1, we get new "problem" issue numbers, which we deal with in the same way as the 210 existing github issue numbers.

--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
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:
1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
2. The numbering can be fully-controlled.
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.

We could also just have <a href="http://llvm.org/PR###">llvm.org/PR### 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).

Then we could introduce a new naming scheme for github issue shortlinks.

On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email]> wrote:
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.

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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
 
The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
On 2020-04-20, Richard Smith via cfe-dev wrote:

>On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev <
>[hidden email]> wrote:
>
>> > If we are reasonably certain that no one would be opening new issues on
>> GitHub while the migration is running...
>> And pull requests (the numbering is common for issues and pull
>> requests) as well. And we cannot disable pull requests at all. And I'm
>> afraid the issues will need to be opened as well during the migration.
>> And now the real problem: should an "extra" pull request or issue
>> intervene in the migration there is no way to "reset" the counter
>> besides deleting the project and creating it once again. We could only
>> sacrifice some bugzilla issues to restore the numbering...
>>
>
>We can edit summaries and comments, presumably by API calls as well as by
>the web UI. So how about this:
>
>Step 1: Preallocate sufficient github issue numbers. Make a bot account and
>with it file empty placeholder issues until we have N issues total, where N
>is the number of bugzilla bugs.
>Step 2: Shut down the ability to file new bugzilla bugs, double-check we
>have enough placeholder bugs, then open up github for new issue
>submissions. Change llvm.org/PRxxxxx to redirect to github for xxxxx's
>higher than the transition point.
>Step 3a: For each issue filed by the bot account, sync that bug's contents
>to the bugzilla entry: copy across the subject, all the comments, tags, and
>so on.
>Step 3b: For each issue not filed by the bot account whose number is that
>of a bugzilla entry, file a new github bug and sync it with the bugzilla
>bug then add a tracking comment to the github bug saying what the new
>number is.
>
>All we would need to do before we switch systems is steps 1 and 2. The data
>import can be done incrementally with no time constraints. Once transition
>is complete, we can change llvm.org/PRxxxxx (and existing bugzilla links,
>since I'm sure they exist in the wild too) to redirect to github, and shut
>down our bugzilla instance.
>
>If new PRs are filed during step 1, we get new "problem" issue numbers,
>which we deal with in the same way as the 210 existing github issue numbers.

Not sure about the API throttling, ideally we can create a new
repository, write a script and allocate a github issue X for each
bugzilla issue X in some repository. We can then gradually copy comments
to that repository.

After contents are migrated, add a redirector llvm.org/PRxxxxx -> https://github.com/llvm/some-repository/issue/xxxxx
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
Hi,

How is the user workflow to file bugs? Do we have some sort of template? Do they have to pick a label?

Thanks,

-- 
Mehdi


On Mon, Apr 20, 2020 at 12:30 PM Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.


The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On 04/20/2020 09:15 PM, Mehdi AMINI wrote:
> Hi,
>
> How is the user workflow to file bugs? Do we have some sort of template? Do they have to pick a label?
>

We don't have any templates defined yet, we need someone to volunteer to
do this.

Users would not be required to pick a label, they would either use a template
which would add the label automatically or pick a label they felt was relevant.

-Tom

> Thanks,
>
> --
> Mehdi
>
>
> On Mon, Apr 20, 2020 at 12:30 PM Tom Stellard via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     Hi,
>
>     I wanted to continue discussing the plan to migrate from Bugzilla to Github.
>     It was suggested that I start a new thread and give a summary of the proposal
>     and what has changed since it was originally proposed in October.
>
>     == Here is the original proposal:
>
>     http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
>
>     == What has changed:
>
>     * You will be able to subscribe to notifications for a specific issue
>       labels.  We have a proof of concept notification system using github actions
>       that will be used for this.
>
>     * Emails will be sent to llvm-bugs when issues are opened or closed.
>
>     * We have the initial list of labels: https://github.com/llvm/llvm-project/labels
>
>     == Remaining issue:
>
>     * There is one remaining issue that I don't feel we have consensus on,
>     and that is what to do with bugs in the existing bugzilla.  Here are some options
>     that we have discussed:
>
>     1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
>     still active will be updated there until they are closed.  This means that over
>     time the number of active bugs in bugzilla will slowly decrease as bugs are closed
>     out.  Then at some point in the future, all of the bugs from bugzilla will be archived
>     into their own GitHub repository that is separate from the llvm-project repo.
>
>     2. Same as 1, but also create a migration script that would allow anyone to
>     manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
>     repo.  The intention with this script is that it would be used to migrate high-traffic
>     or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
>     This would not be used for mass migration of all the bugs.
>
>     3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
>     Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
>     would be migrated to the llvm-project repo.
>
>
>     The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
>     to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
>     to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
>     transition (proposal 3) will delay the transition for a while (likely several months)
>     while we evaluate the various solutions for moving bugs from bugzilla to GitHub.
>
>
>     The original proposal was to do 1 or 2, however there were some concerns raised on the list
>     that having 2 different places to search for bugs for some period of time would
>     be very inconvenient.  So, I would like to restart this discussion and hopefully we can
>     come to some kind of conclusion about the best way forward.
>
>     Thanks,
>     Tom
>
>     _______________________________________________
>     LLVM Developers mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
On 04/20/2020 04:08 PM, James Y Knight wrote:
> 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:
> 1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
> 2. The numbering can be fully-controlled.
> 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.
>

This seems like a good approach to me.

> We could also just have llvm.org/PR### <<a href="http://llvm.org/PR###">http://llvm.org/PR###> 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).
>

Would we even need a mapping file for this if we are able to get bugzilla id N
to be archived to GitHub issue id N?

-Tom

> Then we could introduce a new naming scheme for github issue shortlinks.
>
> On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>         Hi,
>
>         I wanted to continue discussing the plan to migrate from Bugzilla to Github.
>         It was suggested that I start a new thread and give a summary of the proposal
>         and what has changed since it was originally proposed in October.
>
>         == Here is the original proposal:
>
>         http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
>
>         == What has changed:
>
>         * You will be able to subscribe to notifications for a specific issue
>           labels.  We have a proof of concept notification system using github actions
>           that will be used for this.
>
>         * Emails will be sent to llvm-bugs when issues are opened or closed.
>
>         * We have the initial list of labels: https://github.com/llvm/llvm-project/labels
>
>         == Remaining issue:
>
>         * There is one remaining issue that I don't feel we have consensus on,
>         and that is what to do with bugs in the existing bugzilla.  Here are some options
>         that we have discussed:
>
>         1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
>         still active will be updated there until they are closed.  This means that over
>         time the number of active bugs in bugzilla will slowly decrease as bugs are closed
>         out.  Then at some point in the future, all of the bugs from bugzilla will be archived
>         into their own GitHub repository that is separate from the llvm-project repo.
>
>         2. Same as 1, but also create a migration script that would allow anyone to
>         manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
>         repo.  The intention with this script is that it would be used to migrate high-traffic
>         or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
>         This would not be used for mass migration of all the bugs.
>
>         3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
>         Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
>         would be migrated to the llvm-project repo.
>
>
>     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 llvm.org/PRxxxxx <http://llvm.org/PRxxxxx>, and if we can preserve all the issue numbers this would ease the transition pain substantially.
>      
>
>         The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
>         to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
>         to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
>         transition (proposal 3) will delay the transition for a while (likely several months)
>         while we evaluate the various solutions for moving bugs from bugzilla to GitHub.
>
>
>         The original proposal was to do 1 or 2, however there were some concerns raised on the list
>         that having 2 different places to search for bugs for some period of time would
>         be very inconvenient.  So, I would like to restart this discussion and hopefully we can
>         come to some kind of conclusion about the best way forward.
>
>         Thanks,
>         Tom
>
>         _______________________________________________
>         LLVM Developers mailing list
>         [hidden email] <mailto:[hidden email]>
>         https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>     _______________________________________________
>     LLVM Developers mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
> On 04/20/2020 04:08 PM, James Y Knight wrote:
> > 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:
> > 1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
> > 2. The numbering can be fully-controlled.
> > 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.
> This seems like a good approach to me.
This might work, yes.

There are some limitations as well, this is why I'm very cautious
here. See https://docs.google.com/document/d/1byEcbsxF3pL-HGGd_K6axdh87tbcsuJK3Dp6ThxGjKA/edit
for some list.

>
> > We could also just have llvm.org/PR### <<a href="http://llvm.org/PR###">http://llvm.org/PR###> 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).
> >
>
> Would we even need a mapping file for this if we are able to get bugzilla id N
> to be archived to GitHub issue id N?
>
> -Tom
>
> > Then we could introduce a new naming scheme for github issue shortlinks.
> >
> > On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
> >
> >     On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
> >
> >         Hi,
> >
> >         I wanted to continue discussing the plan to migrate from Bugzilla to Github.
> >         It was suggested that I start a new thread and give a summary of the proposal
> >         and what has changed since it was originally proposed in October.
> >
> >         == Here is the original proposal:
> >
> >         http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
> >
> >         == What has changed:
> >
> >         * You will be able to subscribe to notifications for a specific issue
> >           labels.  We have a proof of concept notification system using github actions
> >           that will be used for this.
> >
> >         * Emails will be sent to llvm-bugs when issues are opened or closed.
> >
> >         * We have the initial list of labels: https://github.com/llvm/llvm-project/labels
> >
> >         == Remaining issue:
> >
> >         * There is one remaining issue that I don't feel we have consensus on,
> >         and that is what to do with bugs in the existing bugzilla.  Here are some options
> >         that we have discussed:
> >
> >         1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
> >         still active will be updated there until they are closed.  This means that over
> >         time the number of active bugs in bugzilla will slowly decrease as bugs are closed
> >         out.  Then at some point in the future, all of the bugs from bugzilla will be archived
> >         into their own GitHub repository that is separate from the llvm-project repo.
> >
> >         2. Same as 1, but also create a migration script that would allow anyone to
> >         manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
> >         repo.  The intention with this script is that it would be used to migrate high-traffic
> >         or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
> >         This would not be used for mass migration of all the bugs.
> >
> >         3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
> >         Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
> >         would be migrated to the llvm-project repo.
> >
> >
> >     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 llvm.org/PRxxxxx <http://llvm.org/PRxxxxx>, and if we can preserve all the issue numbers this would ease the transition pain substantially.
> >
> >
> >         The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
> >         to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
> >         to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
> >         transition (proposal 3) will delay the transition for a while (likely several months)
> >         while we evaluate the various solutions for moving bugs from bugzilla to GitHub.
> >
> >
> >         The original proposal was to do 1 or 2, however there were some concerns raised on the list
> >         that having 2 different places to search for bugs for some period of time would
> >         be very inconvenient.  So, I would like to restart this discussion and hopefully we can
> >         come to some kind of conclusion about the best way forward.
> >
> >         Thanks,
> >         Tom
> >
> >         _______________________________________________
> >         LLVM Developers mailing list
> >         [hidden email] <mailto:[hidden email]>
> >         https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
> >     _______________________________________________
> >     LLVM Developers mailing list
> >     [hidden email] <mailto:[hidden email]>
> >     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
>
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
Please could we replace the "llvm-tools" with a single label for each LLVM tool (i.e. labels for llvm-ar, llvm-as, llvm-cxxfilt, llvm-objdump etc etc). As mentioned on multiple occasions now, this is much more user-friendly both for people filing issues, and for those like myself who are only interested in certain tools within the tools directory. New bugs can easily be attributed to the tool by finding the label that matches the executable name. As for subscribing, there are many llvm-* tools that I am not interested in because they have nothing to do with the toolchain my company provides. Being subscribed to all bugs in relation to this simply will result in me getting extra noise in my inbox, leading me to be more inclined to ignore things and thus miss items that I'm actually interested in. This will therefore reduce the volume of triage done, which in turn will have a negative impact on the quality of the project (both in leaving important bugs unaddressed and in disincentivising people from filing bugs in this area in the future).

Just because a bugzilla component doesn't get high traffic doesn't mean it isn't useful.

Strong -1 to the migration until this has been addressed, as my previous concerns seem to be being ignored.

See also http://lists.llvm.org/pipermail/llvm-dev/2018-November/127692.html (why we shouldn't limit bugzilla components based on numbers of bugs filed), and my thread here http://lists.llvm.org/pipermail/llvm-dev/2020-March/139953.html (which included discussions on triage groups, and how some of us are quite focused on small areas, all of which are related).

Regards,

James

On Mon, 20 Apr 2020 at 20:31, Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.


The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
Hi James,

> Please could we replace the "llvm-tools" with a single label for each LLVM tool (i.e. labels for llvm-ar, llvm-as, llvm-cxxfilt, llvm-objdump etc etc).
Sorry, I missed the subcomponents for the tools when I did the
migration of the labels. Will add them!

--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
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)).

But I understand the single numbering preserving option is likely more complicated/costly & thus not an equal candidate - just my minor preference.

On Mon, Apr 20, 2020 at 9:58 PM Tom Stellard via llvm-dev <[hidden email]> wrote:
On 04/20/2020 04:08 PM, James Y Knight wrote:
> 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:
> 1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
> 2. The numbering can be fully-controlled.
> 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.
>

This seems like a good approach to me.

> We could also just have llvm.org/PR### <http://llvm.org/PR###> 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).
>

Would we even need a mapping file for this if we are able to get bugzilla id N
to be archived to GitHub issue id N?

-Tom

> Then we could introduce a new naming scheme for github issue shortlinks.
>
> On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>         Hi,
>
>         I wanted to continue discussing the plan to migrate from Bugzilla to Github.
>         It was suggested that I start a new thread and give a summary of the proposal
>         and what has changed since it was originally proposed in October.
>
>         == Here is the original proposal:
>
>         http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
>
>         == What has changed:
>
>         * You will be able to subscribe to notifications for a specific issue
>           labels.  We have a proof of concept notification system using github actions
>           that will be used for this.
>
>         * Emails will be sent to llvm-bugs when issues are opened or closed.
>
>         * We have the initial list of labels: https://github.com/llvm/llvm-project/labels
>
>         == Remaining issue:
>
>         * There is one remaining issue that I don't feel we have consensus on,
>         and that is what to do with bugs in the existing bugzilla.  Here are some options
>         that we have discussed:
>
>         1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
>         still active will be updated there until they are closed.  This means that over
>         time the number of active bugs in bugzilla will slowly decrease as bugs are closed
>         out.  Then at some point in the future, all of the bugs from bugzilla will be archived
>         into their own GitHub repository that is separate from the llvm-project repo.
>
>         2. Same as 1, but also create a migration script that would allow anyone to
>         manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
>         repo.  The intention with this script is that it would be used to migrate high-traffic
>         or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
>         This would not be used for mass migration of all the bugs.
>
>         3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
>         Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
>         would be migrated to the llvm-project repo.
>
>
>     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 llvm.org/PRxxxxx <http://llvm.org/PRxxxxx>, and if we can preserve all the issue numbers this would ease the transition pain substantially.
>     
>
>         The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
>         to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
>         to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
>         transition (proposal 3) will delay the transition for a while (likely several months)
>         while we evaluate the various solutions for moving bugs from bugzilla to GitHub.
>
>
>         The original proposal was to do 1 or 2, however there were some concerns raised on the list
>         that having 2 different places to search for bugs for some period of time would
>         be very inconvenient.  So, I would like to restart this discussion and hopefully we can
>         come to some kind of conclusion about the best way forward.
>
>         Thanks,
>         Tom
>
>         _______________________________________________
>         LLVM Developers mailing list
>         [hidden email] <mailto:[hidden email]>
>         https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>     _______________________________________________
>     LLVM Developers mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev

+1 to James's take

I'd prefer simplicity of implementation over perfection here.

Philip

On 4/20/20 4:08 PM, James Y Knight via llvm-dev wrote:
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:
1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
2. The numbering can be fully-controlled.
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.

We could also just have <a href="http://llvm.org/PR###" moz-do-not-send="true">llvm.org/PR### 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).

Then we could introduce a new naming scheme for github issue shortlinks.

On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email]> wrote:
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.

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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
 
The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Fangrui Song via cfe-dev
On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev <[hidden email]> wrote:

+1 to James's take

I'd prefer simplicity of implementation over perfection here.

If we end up with two different bug numbering systems, that's a problem that we will be paying for for many years. It's worth some investment now to avoid that problem. And it doesn't seem like it really requires much investment.

Here's another path we could take:

1) Fork the llvm repository to a private "bugs" repository. Mirror the bugzilla issues there. Iterate until we're happy, as per James's proposal.
2) Sync the forked repository to the llvm repository, delete the llvm repository, rename "bugs" to "llvm", and make it public.

Then we'll have the first N bugs in llvm-project/llvm being *exactly* the bugzilla bugs, and we'll have excised the existing github issues that we want to pretend never existed anyway.


I think we've missed an important step in the planning here: we've not agreed on a set of goals for the transition. Here are mine:

 * We end up with one single issue tracking system containing all issues, both old and new, both open and closed.
 * All links and references to existing bugs still work.
 * We have a single bug numbering system covering all bugs, and old bugs retain their numbers.

It sounds like we don't all agree that the last point is important, but if we can achieve it without any significant additional cost, why not do so?

Philip

On 4/20/20 4:08 PM, James Y Knight via llvm-dev wrote:
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:
1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.
2. The numbering can be fully-controlled.
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.

We could also just have llvm.org/PR### 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, https://gcc.gnu.org/pipermail/gcc/2020-April/232030.html).

Then we could introduce a new naming scheme for github issue shortlinks.

On Mon, Apr 20, 2020 at 3:50 PM Richard Smith via llvm-dev <[hidden email]> wrote:
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev <[hidden email]> wrote:
Hi,

I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.

== Here is the original proposal:

http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html

== What has changed:

* You will be able to subscribe to notifications for a specific issue
  labels.  We have a proof of concept notification system using github actions
  that will be used for this.

* Emails will be sent to llvm-bugs when issues are opened or closed.

* We have the initial list of labels: https://github.com/llvm/llvm-project/labels

== Remaining issue:

* There is one remaining issue that I don't feel we have consensus on,
and that is what to do with bugs in the existing bugzilla.  Here are some options
that we have discussed:

1. Switch to GitHub issues for new bugs only.  Bugs filed in bugzilla that are
still active will be updated there until they are closed.  This means that over
time the number of active bugs in bugzilla will slowly decrease as bugs are closed
out.  Then at some point in the future, all of the bugs from bugzilla will be archived
into their own GitHub repository that is separate from the llvm-project repo.

2. Same as 1, but also create a migration script that would allow anyone to
manually migrate an active bug from bugzilla to a GitHub issue in the llvm-project
repo.  The intention with this script is that it would be used to migrate high-traffic
or important bugs from bugzilla to GitHub to help increase the visibility of the bug.
This would not be used for mass migration of all the bugs.

3. Do a mass bug migration from bugzilla to GitHub and enable GitHub issues at the same time.
Closed or inactive bugs would be archived into their own GitHub repository, and active bugs
would be migrated to the llvm-project repo.

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 llvm.org/PRxxxxx, and if we can preserve all the issue numbers this would ease the transition pain substantially.
 
The key difference between proposal 1,2 and 3, is when bugs will be archived from bugzilla
to GitHub.  Delaying the archiving of bugs (proposals 1 and 2) means that we can migrate
to GitHub issues sooner (within 1-2 weeks), whereas trying to archive bugs during the
transition (proposal 3) will delay the transition for a while (likely several months)
while we evaluate the various solutions for moving bugs from bugzilla to GitHub.


The original proposal was to do 1 or 2, however there were some concerns raised on the list
that having 2 different places to search for bugs for some period of time would
be very inconvenient.  So, I would like to restart this discussion and hopefully we can
come to some kind of conclusion about the best way forward.

Thanks,
Tom

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
LLVM Developers mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
123