From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Joseph Myers <josmyers@redhat.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Re: Hashing out the scope of work
Date: Mon, 29 Apr 2024 14:52:41 -0400 [thread overview]
Message-ID: <060ff9e5-785a-4963-8d92-2638db3228da@gotplt.org> (raw)
In-Reply-To: <6d25ccc7-ef3e-a885-b085-51185c23c91@redhat.com>
On 2024-04-29 12:35, Joseph Myers wrote:
>>>> 6. Patch tracking services (Patchwork)
>>>>
>>>> a. LF will deploy the latest version of Patchwork patch tracking software
>>>> under patchwork.coretoolchain.dev.
>>>> b. LF will set up automation and integration services between mailing lists,
>>>> patchwork, and git repositories (using [git-patchwork-bot][8]).
>>>> c. LF will work with the glibc community to set up projects and access as
>>>> appropriate.
>>>
>>> The existing glibc Patchwork database should be transitioned across.
>>
>> Can you give more information why this is desired? This is uncharted
>> territory and I'm not sure how much effort this would require.
>
> The same reason as anything else. Patches from before the transition are
> just as much in need of review as those from after the transition, so the
> state of review of those patches should be maintained across the
> transition.
>
> I don't really think of moving patch review state or bug database state
> across as substantially different from moving the existing git repository
> - these are all key parts of the development process and shouldn't have an
> artificial divide based on the details of when hosting changed, once the
> transition happens developers should only need to interact with the new
> system, for tracking state of old or new patches, for updating state of
> old or new bugs.
I believe we had explicitly agreed in a previous CTI TAC meeting to
start over with a clean slate for patchwork and not bother with
migrating the previous database.
If the active patch backlog is a concern then maybe we could refer to
both instances for a while in the patch review call and move over
completely at the end of that period. I don't remember ever managing to
actually run through the full backlog (that currently stands at 469
patches) during any review session.
Sid
next prev parent reply other threads:[~2024-04-29 19:01 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 [this message]
2024-04-29 20:47 ` Joseph Myers
2024-04-29 21:01 ` Konstantin Ryabitsev
2024-04-29 21:58 ` Joseph Myers
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=060ff9e5-785a-4963-8d92-2638db3228da@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=josmyers@redhat.com \
--cc=konstantin@linuxfoundation.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).