llvm dev - Dec 2021 - [cfe-dev] Status of Bugzilla Migration

Hello Arthur,
> FWIW, "20 hours" or "11 hours" or "three
days" is like nothing, compared to what the migration has already been
doing. If it only requires taking Bugzilla down for 24 hours to do it, IMO you
should just do it already — whatever "it" is.
Well, it's for single sweep. So, if we'd need to do this, say 5 times,
then everything starts to be very interesting.
> Also, re timestamps: The choices seem to be
> - Wait for GitHub to offer us some way of importing timestamps, then do the
migration; or
> - Do the migration, then wait for GitHub to offer us some way of
retroactively changing some of the timestamps.
> Neither is perfect, but the latter is clearly better for LLVM's
purposes.
Not the timestamps, the labels. And note that there is nothing in
general that could be done in GitHub retroactively. At least for us as
I've been told. If this would be possible we'd simply import into an
empty repo, add git repo, add releases (dating them into the past) and
we're done...

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

>From my experience adding a label to an issue does not trigger any
notifications (though it can trigger web hooks), so I think that shouldn't
cause problems. Also agree that being able to retroactively edit edited
time on GitHub is almost certainly not going to happen, whereas GitHub
fixing their repo migration to preserve labels seems likely. One question,
Anton, did you create the labels in the target repo before trying the
migration? Just a vague hypothesis that perhaps it might preserve them if
the labels already exist, but drop them if they don't (pure speculation,
but plausible enough to be worth testing out IMO).

On Thu, Dec 2, 2021 at 11:19 AM Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello Arthur,
>
> > FWIW, "20 hours" or "11 hours" or "three
days" is like nothing, compared
> to what the migration has already been doing. If it only requires taking
> Bugzilla down for 24 hours to do it, IMO you should just do it already —
> whatever "it" is.
> Well, it's for single sweep. So, if we'd need to do this, say 5
times,
> then everything starts to be very interesting.
>
> > Also, re timestamps: The choices seem to be
> > - Wait for GitHub to offer us some way of importing timestamps, then
do
> the migration; or
> > - Do the migration, then wait for GitHub to offer us some way of
> retroactively changing some of the timestamps.
> > Neither is perfect, but the latter is clearly better for LLVM's
purposes.
> Not the timestamps, the labels. And note that there is nothing in
> general that could be done in GitHub retroactively. At least for us as
> I've been told. If this would be possible we'd simply import into
an
> empty repo, add git repo, add releases (dating them into the past) and
> we're done...
>
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211202/805663d6/attachment.html>