P. L. Lim

Please use the new `perf` change log category, see: * https://github.com/astropy/astropy/pull/16694

> this backported into a bugfix But this is technically new API and I don't see the lack of this being blocker of anything downstream, so I prefer not to...

> there isn't really much benefit in holding it back and thus delaying the ability to use it Then the same argument can be applied to user features too going...

@nabobalis , there appears to be disagreement on milestone (and hence change log section). But in the meantime, does your checkbox of "fix the test" still applies?

Would need a rebase for CI. I am moving the milestone because I think it is a bit too late in the release cycle now for the VO people downstream....

Why the keep-open label? A simple rebase would have give you another 6 months. Also, there is a conflict so it needs a rebase anyway.

Not if you come back and remove the label later after a rebase. Excessive use of keep-open label defeats the purpose of the stale bot.

There is also a TBD under "sequence" in https://jwst.readthedocs.io/en/latest/jwst/associations/level3_asn_rules.html

linkcheck failure is unrelated.

I *think* this is because asdf-astropy pulls in asdf, and unfortunately, asdf itself ships its own pytest plugin within the package (as opposed to separate plugin package): https://github.com/asdf-format/asdf/blob/main/pytest_asdf/plugin.py Even so,...