What should the relationship between ports and developers of large projects be?

[Andrew Haley]

On 5/28/22 08:21, Thomas Stüfe wrote:
> Stating the obvious, it helps if large patches were split up into smaller ones. The loom patch brought my browser to its knees. For that, maybe lower the bar for introducing patches whose sole purpose is to prepare a larger integration or make merging side projects with mainline easier. I had preparatory patches like these rejected in the past, understandingly, on the ground that they had no merit on their own.

Interesting.

 From what I know of the virtual threads patch, there's a tremendous amount
of interdependence, from the VM to the JVMTI to to the library code, and so
on. I believe it would have been very costly to split up the patch, and it
would have been impossible to test any of it until it was all in.

-- 
Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671