@kernellogger@jann It's not just "unusual" that a cycle takes longer than 70 days, it has only happened twice in the last 15 years: 3.1 (slowed by the kernel.org compromise) and 4.15 (the meltdown/spectre release). It takes an event of that magnitude to slow things down at this point.
I'm not sure if we can realistically make the cycle shorter - some problems just take time to turn up and to be fixed.
As is normal, the September report says that all is great with the project - community health is always "improving". And they are clearly on top of upcoming problems: "Python 2 is unmaintained. We have in the development tree the external python3 support. Internal python 3 support is difficult. We are checking alternatives." They plan to fix it in "the next major release". The project hasn't made a major release in ten years, so I wouldn't hold my breath...
(OK, so I'm still clearly in a snarky mode, sorry.)
GnuCash fixed this upstream on October 26, but has not made a release with the fix, so my 5.9 Fedora version showed the bug in all its glory. I've submitted a bug there (https://bugzilla.redhat.com/show_bug.cgi?id=2323303), hopefully they will include the fix soon. Meanwhile, I strongly recommend that anybody with GnuCash 5.9 installed be extra careful.
*Edited* since people are asking: NAK (or NACK) comes (I believe) from the ASCII negative-acknowledge character. In this context, is an abrupt way for a maintainer to reject a patch.
On the radar: what is the linux-kernel mailing list for? @monsieuricon is suggesting that many or most patch postings be redirected to a separate list:
I've not jumped into the conversation because I'm still trying to figure out what I think about it. I'm one of those people who actually reads over that list; the broad view it provides is helpful in both the LWN and documentation-maintainer roles. But it *is* painful to keep up with.
LKML has traditionally been the place you post patches to get them reviewed. If that's not its role anymore, what is it for?
@adamw@bars@marcan Bug tracking is clearly a place where the kernel project falls down badly, agreed. We finally got regression tracking funded, but that's just barely the beginning of the problem.
For bug tracking, one aspect of the problem is a simple unwillingness on the part of many maintainers to bother with a bug tracker. That does not help at all.
The other part is something I'm going to poke people at the LF shindig about next week. Almost everybody who works on the kernel is paid to do it, but there are many areas that no company thinks it needs to worry about funding. Of the 5,000 developers who work on the kernel each year, not a single one of them is tasked with documentation — my own pet peeve. But (almost) nobody is paid to work on tools, and it hurts us in all kinds of ways, including bug tracking.
@marcan@bars One of the worst things about working in the kernel — one of the most toxic parts — is the constant stream of nastiness toward our community that comes from outside.
The kernel community is far from perfect; we have a lot of problems and we have been actively working for years (decades) to improve on them.
We are, nonetheless, a project that manages to incorporate nearly 100,000 commits per year, from over 5,000 developers, into a single code base while maintaining a level of quality that — while also certainly in need of improvement — is good enough for deployment into billions of devices.
As for the use of email...email is painful and broken, but we have found nothing better that will work at the scale we need. See https://lwn.net/Articles/702177/ from a few years back. For all its faults, email is distributed, non-proprietary, scriptable, and gives everybody the freedom to choose their tools; it is a highly inclusive solution in a way that proprietary web forges (for example) are not. Someday we'll find something better and move on with a cry of joy, but that day has not come.
Rather than crapping on the kernel community from afar, why not work with us to try to make things better?
@liw@neil@pwaring Surprisingly, I have a *lot* of sympathy for people trying to earn their living with their writing. It's not an easy path, and you have to pick your poison... whether it's overt paywalls, annoying popups, or surveillance advertising, it's going to be annoying to people.
We've found a solution that works well enough for LWN - at least, well enough to keep us from having to get real jobs - but I'm not sure what the best solution is in a general sense.