General Questions about bugzilla / feature requests

[RoxyProxy]

Hello there people,

I have a general Question about a feature request specifically this one: Bug 4693 - [Feature Request] - PVE - TPM State Disk as qcow2
This is a feature I and many others are very much looking forward to, and I have seen on the lore site that Fiona Ebner has already done some progress and someone has already tested the feature. https://lore.proxmox.com/pve-devel/20251014143946.160679-1-f.ebner@proxmox.com/T/

Now this feature requests status is "PATCH AVAILABLE".

I wanted to ask what this means, does this mean that there is a patch but only in a non-public development branch?
Or does it mean that its already available in the pve-test repo? Because I have tested with the pve-test repo and wasn't able to have tpm disks in qcow2 format, or did I just miss a setting I have to change?

Also is there any timeframe when we will see the feature in the test or no-subscription repositories if it is still in a closed branch?

I also noticed that anyone who has an account on bugzilla would be able to change many or all of the information of a request even though they werent the creator of said request.
Isn't this a bit of a risk?

I'm a bit confused and it'd be awesome if someone could help me understand this a bit more clearly.
Thanks!

 

[fabian]

PATCH AVAILABLE means there is a patch on the corresponding mailing list

after it has been applied, the status moves either to FIX PACKAGED (it's in git, but not yet released in a package) or RESOLVED FIXED (if the package is already bumped).

sometimes the bug status can lag behind a bit.

I wanted to ask what this means, does this mean that there is a patch but only in a non-public development branch?
Or does it mean that its already available in the pve-test repo? Because I have tested with the pve-test repo and wasn't able to have tpm disks in qcow2 format, or did I just miss a setting I have to change?

Also is there any timeframe when we will see the feature in the test or no-subscription repositories if it is still in a closed branch?

there are normally no non-public development branches, except for convenience for bigger patch series, or for embargoed security fixes. developers usually apply patches from the list (archives), build the packages themselves and test the result.

there are normally no ETAs for how fast things move along, but from applied in git to contained in a test package in the public APT repo it is usually not too long (think a few weeks at most).

I also noticed that anyone who has an account on bugzilla would be able to change many or all of the information of a request even though they werent the creator of said request.
Isn't this a bit of a risk?

all changes there are revertible, and we get notifications for all of them

 

[RoxyProxy]

That was quick!
Thank you Fabian!

I'll try to be patient, but I'm still excited for this feature

I do have another quick question not fully related.
How long is the delay usually till a feature introduced in the pve-test repository is also available in the non-subscription repo,
and how long is the delay usually till a non-subscription feature is then tested enough that its available in the enterprise repository?

 

[fabian]

that is very variable, it depends how big/risky and/or urgent the delta is, how interconnected it is with other packages currently moving along, etc.pp.