From: Joseph Myers <josmyers@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
cti-tac@lists.linuxfoundation.org
Subject: Re: Hashing out the scope of work
Date: Mon, 29 Apr 2024 21:58:18 +0000 (UTC) [thread overview]
Message-ID: <30dc33a-69de-39e6-fe7d-bd21c99ccecf@redhat.com> (raw)
In-Reply-To: <20240429-rousing-mamba-of-improvement-cabefb@lemur>
On Mon, 29 Apr 2024, Konstantin Ryabitsev wrote:
> For example, for bugzilla we'd need to prepare a query to filter bugs
> and comments by product and component -- to only include those belonging
> to glibc. However, how do we go about filtering users? User records are
> not tied to a specific product or component. We can try to have a large
> query limiting the users to just those accounts who have commented on
> glibc bugs, but this is going to be hairy -- someone could have
> commented on a bug that started out filed under a different
> product/component.
The simple answer there is not to filter users. It's OK to have more
users than necessary in the new database.
We do still need to make sure things don't break if migrating a bug that
was originally reported under a different product/component, whose history
might thus show changes of product/component/... from values that
shouldn't need to exist in the new Bugzilla. But as long as things don't
break, it's OK for the history display not to show those details of the
history that aren't meaningful in a glibc-only context - to show them as a
change from <missing-product> to glibc, for example.
> The same problem is with patchwork -- migrating just the subset of the
> database that belongs to glibc lists is going to be very difficult,
> especially with the kind of data model that patchwork has. Is it the CI
> data that you want to preserve?
I think it's the details of what patches / patch series still need review
that's the most valuable part to preserve and migrate.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-04-29 21:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 16:45 Hashing out the scope of work Konstantin Ryabitsev
2024-04-24 21:15 ` Ian Kelling
2024-04-25 1:31 ` Konstantin Ryabitsev
2024-04-25 20:06 ` Ian Kelling
2024-04-26 16:06 ` Siddhesh Poyarekar
2024-05-13 17:28 ` Carlos O'Donell
2024-04-29 14:09 ` Joseph Myers
2024-04-29 15:23 ` Konstantin Ryabitsev
2024-04-29 16:35 ` Joseph Myers
2024-04-29 18:52 ` Siddhesh Poyarekar
2024-04-29 20:47 ` Joseph Myers
2024-04-29 21:01 ` Konstantin Ryabitsev
2024-04-29 21:58 ` Joseph Myers [this message]
2024-04-30 12:30 ` Konstantin Ryabitsev
2024-04-30 12:41 ` Siddhesh Poyarekar
2024-05-02 19:27 ` Joseph Myers
2024-05-07 20:36 ` Konstantin Ryabitsev
2024-05-07 21:45 ` Joseph Myers
2024-05-13 16:31 ` Carlos O'Donell
2024-05-17 21:22 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30dc33a-69de-39e6-fe7d-bd21c99ccecf@redhat.com \
--to=josmyers@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=siddhesh@gotplt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).