Excellent work, it is deeply appreciated. And yeah, it would be nice if some future work could change the location of that automated traffic. I feel like merging the 2 into a *-dev mailing list just drowns out the actual discussion.
For example, good luck getting a word in edge-wise on the core-libs-dev <https://mail.openjdk.org/archives/list/[email protected]/2026/8/?count=200&page=4> mailing list, where in the 3 days since August started, they have managed to pump out 39 different threads, all of which are automated. I've made posts on that mailing list that get missed, but end up being useful reports when finally picked up. And to be clear, automated traffic is both good and important. I just feel like it belongs on it's own mailing list. Probably a *-rfr or a *-repo mailing list, and keep *-dev for the actual discussions. I understand that maybe not every project/mailing-list/initiative would care to do this. For example, amber-dev isn't nearly as busy. But imo, it's a good idea for all jdk mailing lists, not just valhalla-dev. On Tue, Aug 4, 2026 at 7:48 PM Dan Smith <[email protected]> wrote: > Last week we achieved a major development milestone, with JEP 401: Value > Objects (Preview) integrated into the mainline JDK, and the `lworld` branch > closed to any further development. Those features are now part of JDK 28. > Future bug fixes will target the `jdk` repository directly, and future JEPs > will have their own development branches in the `valhalla` repository. > > Historically, this mailing list has been a firehose of development > notifications (my mail client has collected over 6800 messages in the 215 > days since Jan 1!). By closing the `lworld` branch, hopefully we’re turning > the firehose off. > > Going forward, I’d love to see this space be dominated by non-automated > conversations about value objects and other Valhalla features. Preview > features, in particular, are designed for collecting feedback before a > feature is made final, and ideally this mailing list is a lightweight way > for people trying out the feature to share their experiences and learn from > each other. > > Some open-source projects have “user” lists and “developer” lists. OpenJDK > `-dev` lists bridge both of those communities, and hopefully can serve both > of their needs. > > I’m going to keep an eye out for firehose traffic in next few weeks. If we > start generating a lot of commit or PR messages, I’ll suggest either > turning them off or sending them somewhere else. I think most people are > happy to handle PRs directly through the GitHub UI, for example. (I *think* > all the traffic may have been due to optional configuration settings of the > `lworld` branch, but we’ll see…) > >
