----- Le 26 Sep 19, à 19:02, Thomas Lamprecht t.lampre...@proxmox.com a écrit :
>> >> Thanks to you for reviewing / merging. >> Should I close bug #2384 now ? (not sure if you have some particular >> workflow on >> BZ) > > Hmm, as you're here not only the Reporter but effectively also the > Assignee which patched the issue yourself you have the full rights > to close it. > But, we normally wait until the fix(es) get packaged, else people will > still complain as they do not have it yet available (easily). > Sometimes, if I'm really sure it is fixed, I just close it nonetheless > and write something akin to: > > "Fixed by [reference to commit] in [package] not yet released, should get > available in [current-version + 1]" > > so that I do not forget to close it. For your own bugs you can do as it > seems practical to you in such a case. :) > > cheers, > Thomas OK, thanks. I'll wait for it to be packaged and available in pvetest so if someone find a regression we can continue on this bug. Cheers, Daniel -- [ https://www.firewall-services.com/ ] Daniel Berteaud FIREWALL-SERVICES SAS, La sécurité des réseaux Société de Services en Logiciels Libres Tél : +33.5 56 64 15 32 Matrix: @dani:fws.fr [ https://www.firewall-services.com/ | https://www.firewall-services.com ] _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
