From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] is the next pve version 8.0 with debian 12 ? (any planning on patches merge ?)
Date: Fri, 28 Apr 2023 07:15:49 +0000 [thread overview]
Message-ID: <5d378b3f9838ed1f8c8cfdb0a807b4890e11d6ea.camel@groupe-cyllene.com> (raw)
Hi,
I would like to known if the next pve version will be 8.0 on debian12 ?
and if they are any planning for patches merging ? (I would like to
schedule time on my agenda if my patches need to be rework).
We had discussed about it last year, but I would like to implement
permissions on vmbrX && sdn vnets, as it a breaking change.
https://git.proxmox.com/?p=pve-manager.git;a=commit;h=a37ff602ff742403f01d6682bf9948183f87eadb
Also, I have a bunch of patches waiting for review or merge. (sorry for
the flood ^_^)
Here the list to be sure that they will not be lost.
[pve-devel] [PATCH v4 qemu-server 00/16] rework memory hotplug +
virtiomem
https://lists.proxmox.com/pipermail/pve-devel/2023-February/055746.html
(waiting for HA to support the new memory format)
[pve-devel] [PATCH pve-manager 0/2] ui: add support for new memory
format
https://lists.proxmox.com/pipermail/pve-devel/2023-February/055834.html
[pve-devel] bump default kvm64 cpumodel to a new x86-64-v2 model ?
https://lists.proxmox.com/pipermail/pve-devel/2023-March/056014.html
(Not a patch yes, just a question, but maybe it could be great to bump
the default cpu model for proxmox 8 ?)
https://lists.proxmox.com/pipermail/pve-devel/2023-March/056107.html
[pve-devel] [PATCH qemu-server 0/6] improve virtio drive multiqueues
(I need to rework this, as it seem buggy when you have a lot of disk,
but add support for virtio disk, and expose the queues option in the
gui should be enough. This is mainly usefull to improve local nvme
speed)
https://lists.proxmox.com/pipermail/pve-devel/2023-March/056366.html
[pve-devel] [PATCH-SERIES qemu, qemu-server, manager 0/1] add tcmalloc
support
(could be really great for ceph users. I'm running it in production
since 2 months without problem)
https://lists.proxmox.com/pipermail/pve-devel/2023-March/056425.html
[pve-devel] [PATCH-SERIES pve-access-control/pve-manager] Add firewall
caps
(I really need this for a customer with audit access only)
some other network fixes:
https://lists.proxmox.com/pipermail/pve-devel/2023-April/056533.html
[pve-devel] [PATCH pve-container] fix #4457: use bridge mtu if no mtu
is defined
https://lists.proxmox.com/pipermail/pve-devel/2023-April/056557.html
[pve-devel] [PATCH frr] fix #4040 : patch : ospf6d: fix infinite loop
when adding ASBR route
https://lists.proxmox.com/pipermail/pve-devel/2023-April/056619.html
[pve-devel] [PATCH pve-network 0/6] sdn multiples fixes
next reply other threads:[~2023-04-28 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 7:15 DERUMIER, Alexandre [this message]
2023-04-28 9:33 ` Thomas Lamprecht
2023-04-28 10:09 ` Fabian Grünbichler
2023-04-28 12:04 ` DERUMIER, Alexandre
2023-04-28 12:15 ` DERUMIER, Alexandre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d378b3f9838ed1f8c8cfdb0a807b4890e11d6ea.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.