[PATCH 1/2] REST: Don't error if a versioned field we would remove is absent
Daniel Axtens
dja at axtens.net
Fri Oct 29 01:49:22 AEDT 2021
Konstantin Ryabitsev <konstantin at linuxfoundation.org> writes:
> On Wed, Oct 27, 2021 at 05:00:34PM +0100, Stephen Finucane wrote:
>> v2.2.6 is available now. Let me know if there are any issues.
>
> Thanks!
>
>> Somewhat related: are there any large blockers preventing you moving to v3.0.x?
>> Is it the major version bump or removal of Python 2.7 support that's preventing
>> the upgrade, or is there something else? In particular, is there anything that
>> we could address? I'd like to get v3.1.0 out before the end of year but I'm
>> slightly concerned that no one (?) has rolled forward to v3.0.x yet :D
>
> The only concern, really, is the data migration and the potential for
> regressions. There are several subsystems now that are reliant on the CI
> aspects of patchwork.kernel.org to track their work, so I'm trying to be
> careful not to disrupt their work. I know that there are some cool new
> features in 3.x that would warrant migrating to it sooner than later -- just
> trying to plan out when is the best time to do it.
>
> On the upside, we're on the cusp of moving the web ui parts to a containerized
> deployment, so perhaps I can trial out the migration to 3.0 as part of that
> work.
I'd probably hold off until I can get some of the pieces to make the
migration more friendly in. I've tried to take on some of your feedback
so it does things like migrate data in chunks rather than all in one
giant statement...
but up to you, of course! Who knows when I will get to them, work has
just decided that we're going to bring forward a feature we had decided
to defer so I am Busy!
Kind regards,
Daniel
>
> -K
More information about the Patchwork
mailing list