▲ | whatagreatboy 3 days ago | ||||||||||||||||
Was there any attempt at making rules for experimental features looser than other filesystems? That seems to be the biggest bottleneck here. | |||||||||||||||||
▲ | koverstreet 3 days ago | parent [-] | ||||||||||||||||
That does seem to be one of the big disconnects, yes. In the past I've argued that I do need a relatively free hand and to be able to move quickly, and explained my reasoning: we've been at the stage of stabilization where the userbase is fairly big, and when someone reports a bug we really need to work with them and fix it in a timely manner in order to keep them testing and reporting bugs. When someone learns the system well enough to report a bug, that's an investment of time and effort on their part, and we don't want to lose that by having them get frustrated and leave. IOW: we need to prioritize working with the user community, not just the developer community. All that's been ignored though, and the other kernel maintainers seem to just want to ratchet down harder and harder and harder on strictness. At this point, we're past the bulk of stabilization, and I've seen (to my surprise) that I've actually been stricter with what I consider a critical fix than other subsystems. So this isn't even about needing special rules for experimental; this is just about having sane and consistent rules, at all. | |||||||||||||||||
|