This step is in some sense final - we cannot undo it since we'll start
doing this. Also, while the import of issues to the empty repo does
not trigger any notifications, the transfer will trigger all kinds of
notifications. We certainly do not want that everyone who contributed
to any issue in the past would receive multiple notifications. For
some active community members the volume of notifications would be
excessive – thousands of emails.
GitHub has a way to disable notifications, however, they found some
issues with it pretty recently. We are waiting for them to resolve it
and expect the final migration to happen within the next 48 hours.
--
With best regards, Anton Korobeynikov
_______________________________________________
flang-dev mailing list
flan...@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev
_______________________________________________
cfe-dev mailing list
cfe...@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
This thought had occurred to me as well. Using a separate repo for bug tracking seems reasonable as an intermediate step. Unless there's a complexity here I'm missing, I'd probably vote for that in favor of going all the way back to bugzilla.
Philip
p.s. Anton, thank you for the update and all the work that has
gone into this.
_______________________________________________ LLVM Developers mailing list llvm...@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
If there are new issues created directly in llvm-bugzilla-archive, and they have cross-references to other (new or old) issues, we’d want to make sure they get fixed up along with the originally-from-bugzilla references. (Recall that all issues will be renumbered when they move to llvm-project.)
It would be mildly annoying to have the bug repo move twice instead of once, but if the reference re-writing works correctly then I don’t have any real objection.
--paulr
>- This has to be done via GitHub API and we're rate limited to ~5000
requests per hour, so this means that the labelling will take ~20
hours. I was told that there is no way for us to have the API rate
limit increased.
This 5000 request per hour limit, is that per repo or per access token? Could we potentially make a pool access token from multiple github accounts to sidestep the issue? Say 20 tokens to do the migration in 1 hour?
The only alternative I'm seeing is to apply the labels post-migration.
There are important downsides:
- This has to be done via GitHub API and we're rate limited to ~5000
requests per hour, so this means that the labelling will take ~20
hours. I was told that there is no way for us to have the API rate
limit increased.
- This might trigger notifications. My quick check via web ui does
not, but I cannot be 100% with anything here
- (the most important) This will screw the "last modified" timestamp
as label setting is an event that is recorded in the issue. There is
no way to set some "old" timestamp, it is assigned by GitHub
automatically.
For now I'm testing the script for 3. and waiting for any news from GitHub.
I will keep you updated.
--
With best regards, Anton Korobeynikov
On behalf of LLVM Foundation
Mehdi wrote:
> Maybe if you can share this on a public repo, others here can help to do small test runs in private forks and cross-validate or help fix issues with it?
I certainly could do this, but I doubt this will be useful as the
input will be a local bugzilla dump..