llvm dev - Dec 2021 - [cfe-dev] [Openmp-dev] Bugzilla migration is stopped again

> The only casualties will be unimportant things:
> github stars, github forks, github release dates;
> but if github can't be bothered to help with those,
> it will serve as a forever reminder to the users that github is unreliable,
> and false dependence should not be created on replaceable unreliable
things.
Thanks for your opinion. However, this was previously discussed and it
was decided that release dates do matter as well as forks. The latter
is even more important for downstream users.

Surely, if the community will re-decide that these are unimportant
things we can push the existing code into a blank archive fairly
quickly.
-- 
With best regards, Anton Korobeynikov

On Sat, Dec 4, 2021 at 1:46 PM Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>
> > The only casualties will be unimportant things:
> > github stars, github forks, github release dates;
> > but if github can't be bothered to help with those,
> > it will serve as a forever reminder to the users that github is
unreliable,
> > and false dependence should not be created on replaceable unreliable
things.
> Thanks for your opinion.
Yep, it is indeed *just* *my* opinion, formed by observing the situation.
> However, this was previously discussed and it
> was decided that release dates do matter as well as forks. The latter
> is even more important for downstream users.
>
> Surely, if the community will re-decide that these are unimportant
> things we can push the existing code into a blank archive fairly
> quickly.
> --
> With best regards, Anton Korobeynikov
Roman

On Sat, Dec 4, 2021 at 5:46 AM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> [...]
> * Surely*, if the community will re-decide that these are unimportant
> things
> *we can push the existing code into a blank archive fairly quickly*.
>
Please, test the above claim this week, *on a blank repo*.  Let's actually
find out whether it works, instead of relying on "Surely...".

At this point I'm offering my own technical assistance, just to get the
thing done and stop getting these emails every day. Send me your Bugzilla
export script; I'll test it out this week on a blank repo, with the goal of
mirroring a 100-bug subset of the LLVM Bugzilla publicly visible in
https://github.com/Quuxplusone/LLVMBugzillaTest/ by EOW.

(Credentials: I was SRE at Mixpanel for ~3 years and performed several
100GB cluster migrations with zero downtime. I *have* seen the "We'll
do it
live!" attitude be successful, but I have also seen it fail spectacularly.
The alternative "plan it carefully, write down your deploy plan, test what
can be tested ahead of time, do a practice run, *then* do it live" approach
usually works better. At this point it looks like Anton's initial pass at
"We'll do it live!" clearly was *not* successful, in the sense
that if it
*were* successful the repo would have been migrated circa Thanksgiving
weekend. So this is the giant-honking-red-flashing-light alert that it's
time to shift from "We'll do it live!" to "Let's make a
deploy plan.")

Respectfully, yet frustrated with the never-ending email thread,
–Arthur
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211204/0680adc0/attachment.html>