llvm dev - Oct 2021 - Update on Bugzilla migration

Dear fellow LLVM contributors and users,

I do apologize for the radio silence on the bugzilla migration and I
do certainly appreciate your patience on this topic. It turned out
that the overall migration process is quite non-trivial given the
amount of data, all kinds of restrictions, rules and regulations we
have to take into account. However now I believe we are very close to
the cut-off point. Here is the sequence of events that will likely
happen later this month:

1. I'd expect that we will perform a test migration of ~3k bugzilla
PRs into a dummy project later this week. Please let me know if you'd
encounter any side-effects of such migration, e.g. excessive
notifications being sent, etc.
2. After the migration we will perform the final check of the
contents: labels, users, cross-links, attachments, etc.
3. If step 2 will yield the content of adequate quality, we will
proceed to the next step. Otherwise we will have to fix the issues
that were found and redo steps 1-2. We will communicate the outcome of
the test migration to the community. We will likely not be able to
make big cosmetic changes at that moment, however, we will try to fix
bugs / usability problems should they appear. Note that ~400 first
bugs will be lost during the migration.
4. After step 3 we will decide on the roadmap of the actual migration.
I'd estimate that we will need to shut down / put bugzilla into
read-only mode for approx ~48-72 hours. We will communicate the
proposed roadmap with the community.
5. After the real migration Bugzilla will be put into read-only mode
for next few months to allow possible migration of any missed data.

--
On behalf of the LLVM Foundation,
Anton Korobeynikov,

Thanks for all the work and updates!

On Mon, Oct 11, 2021 at 10:25 AM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Dear fellow LLVM contributors and users,
>
> I do apologize for the radio silence on the bugzilla migration and I
> do certainly appreciate your patience on this topic. It turned out
> that the overall migration process is quite non-trivial given the
> amount of data, all kinds of restrictions, rules and regulations we
> have to take into account. However now I believe we are very close to
> the cut-off point. Here is the sequence of events that will likely
> happen later this month:
>
> 1. I'd expect that we will perform a test migration of ~3k bugzilla
> PRs into a dummy project later this week. Please let me know if you'd
> encounter any side-effects of such migration, e.g. excessive
> notifications being sent, etc.
> 2. After the migration we will perform the final check of the
> contents: labels, users, cross-links, attachments, etc.
> 3. If step 2 will yield the content of adequate quality, we will
> proceed to the next step. Otherwise we will have to fix the issues
> that were found and redo steps 1-2. We will communicate the outcome of
> the test migration to the community. We will likely not be able to
> make big cosmetic changes at that moment, however, we will try to fix
> bugs / usability problems should they appear. Note that ~400 first
> bugs will be lost during the migration.
> 4. After step 3 we will decide on the roadmap of the actual migration.
> I'd estimate that we will need to shut down / put bugzilla into
> read-only mode for approx ~48-72 hours. We will communicate the
> proposed roadmap with the community.
> 5. After the real migration Bugzilla will be put into read-only mode
> for next few months to allow possible migration of any missed data.
>
> --
> On behalf of the LLVM Foundation,
> Anton Korobeynikov,
> _______________________________________________
> 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/20211011/7ccb35ad/attachment.html>

Dear All,

Here is the status update: the test migration was attempted. First set
of show-stoppers was identified, the majority of them are the
limitations on GitHub side. We are working on circumventing them,
however, there is no ETA yet.

I will keep you informed as soon as new information will be available.

Thank you for your patience and understanding.

--
On behalf of the LLVM Foundation,
Anton Korobeynikov,

Thanks a lot on working on the transition!

Am Mo., 11. Okt. 2021 um 12:25 Uhr schrieb Anton Korobeynikov via
Openmp-dev <openmp-dev at lists.llvm.org>:
> Note that ~400 first
> bugs will be lost during the migration.
I remember it was discussed to create a fresh repository, migrate the
bug ids there, then rename it to llvm-project (since the current
llvm-project really only hosts the git repository) which allows
resetting the namespace counter to one.
My question is, why this path isn't taken?

Michael