Release Planning: v7.6.0

[sirosen]

This is a planning space for the next pip-tools version. It may be retitled if we decide that the next version is a minor or major bump.

v7.5.3 is done, time to start looking forwards!

We have a new milestone up: v7.6.0

Of the items planned, these two are the ones I'm going to try to push forward on:

• [regression][6.10.0] pip-compile hangs on named pipes as input due to double-read #2232
• Introduce an initial LLM Usage Policy #2318

I also intend to look at old/stale PRs to see if we can close some of those up.

[sirosen]

With recent items added, I've updated the milestone from 7.5.4 to 7.6.0! 🎉

In particular, #2358 seems worthy of a minor version bump.

[webknjaz]

💡 @sirosen looking at this, I've been wondering whether we should have another category for maintenance under https://github.com/jazzband/pip-tools/discussions/categories — WDYT? Do we expect contributors to be active in this type of discussions? Does this fall under the announcements category? Is this a type of thing we'd want to be transparent-but-limited-to-maintainers?

[sirosen]

I wouldn't mind a new category if you want, but I'm not sure it's necessary.
I'm happy to follow rather than lead on this subject! 😁

I would like our release planning to be open for anyone to see, and I like allowing for contributors or users to comment if they like. Until we start having problems (e.g., spam), I don't want to restrict conversation. If a user wants to ask about our timelines or priorities, I'm happy to answer.¹

Footnotes

1. Sometimes this can turn into inappropriate nagging, but as long as it's respectful I don't mind sharing. We don't have a major problem with pip-tools users being out of control yet. ↩

[sirosen]

I've just moved almost all items to a new 7.6.1 milestone, leaving only:

• the open issue which tracks that we are not compatible with pip v26.1
• my doc PR which introduces a How-Tos section, which I want very badly for the release

I just got a ping on the compat issue and it prompted me to do this prep work. I really want the docs in for the change in layout on the /stable/ site to land. But as soon as that's merged, I'm ready to prep a release PR.

[sirosen]

I moved #2407 to 7.6.1 as well, as I've been sitting on 7.6.0 for a while. I have a couple of hours today to pour into this, so I'm going to try to prep the 7.6.0 release PR.