3 ms·
> The reason to push it in quickly is so it can get tested and iterated on. Saving a handful of experimental users is not the main benefit. Testing and iterati
by rewgs 1y ago
> The reason to push it in quickly is so it can get tested and iterated on. Saving a handful of experimental users is not the main benefit.
Testing and iterating on code does not require making exceptions to the kernel development schedule.
- Dylan16807 1y agoHe makes a pretty good argument that the filesystem's never going to get done if there's only one iteration per kernel release. I don't know what the best solution is, but it looks like it requires either exceptions or something else that gets around the schedule.
- NekkoDroid 1y agoWell... there is the merge window where this should be added and then like 8 release candidates (as always: it depends) where he can iterate on the added code. So the statement of "only one iteration per kernel release" is just categorically wrong.
- Dylan16807 1y ago"categorically wrong" is a rather uncharitable way to describe you and me using different connotations of the word "iterate". Especially when you pulled "on the added code" out of nowhere. To stabilize the filesystem he needs to iterate on the code that has been there for a while, to add more debugging and fallbacks for error situations. In this case he wanted to add a new fallback.