FreeBSD Bugzilla – Bug 289698 meta-bug for 15.0-RELEASE

[fmc000]

As 15.0 release date is approaching I'm curious to know about the this bug. It depends on many others, a few of them regressions from previous releases.

I'm pretty scared because I'm one of the reporters of a (pretty nasty IMHO) regression from 14.3 that will stop me updating to 15.0 for sure, without a doubt. But even worse IMHO is that I reported the issue three weeks ago and I see no progress, of at least noone contacted me asking for details, tests and so on.

Please don't consider this a rant, it's my major release upgrade and I genuinely don't know how this situations are handled in the FreeBSD world. As of today there are still 12 bugs in the list.

 

[drhowarddrfine]

Please provide a link to the bug report.

As I'm sure you know, RELEASE is RELEASE and anything else is not supported here or anywhere else cause it's still under development.

 

[fmc000]

PR 290265

And yes, I know that anything but RELEASE is not supported here, I'm not complaining about it. I was just looking for clarifications.

 

[W.hâ/t]

As 15.0 release date is approaching I'm curious to know about the this bug.

Description​ Mark Johnston 2025-09-19 15:37:42 UTC A metabug to allow marking of individual bugs as blockers for the release.

I genuinely don't know how this situations are handled in the FreeBSD world.

I dont know either. I would say this is the standard process, with more or less trouble than the previous release.

 

[fmc000]

W.hâ/t yes, it's the "blockers" part I'm most curious about.

 

[SirDice]

As I'm sure you know, RELEASE is RELEASE and anything else is not supported here or anywhere else cause it's still under development.

Wrong, only -CURRENT and EoL versions are not supported here. That said, I've never closed or removed any questions regarding -CURRENT or EoL versions. Just pointed them to Topics about unsupported FreeBSD versions.

 

[Charlie_]

PR 290265

I think it's stopped because the reporter is ignoring the response.
> To make progress, the first step is going to be to see what power state the NVMe drive is in, and whether or not the links to it are up.
> If they are all OK, then we need to maybe look at other things (does this specific drive need addition time to reset maybe?) Also need to make sure that the BARs are save/restored correctly.