From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Mark Schouten <mark@tuxis.nl>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Status Ceph 18.2.1 for enterprise
Date: Fri, 12 Jan 2024 16:01:34 +0100 [thread overview]
Message-ID: <678491c0-6ddb-4478-83ed-7ebc156a99c0@proxmox.com> (raw)
In-Reply-To: <mailman.411.1705063250.335.pve-devel@lists.proxmox.com>
Hi!
Am 12/01/2024 um 13:10 schrieb Mark Schouten via pve-devel:
> What’s the ETA on that? I would like to keep the cluster as ‘enterprise’
> as possible and refrain from mixing repo’s.
No hard ETA, but if nothing comes up we'll move that version over to
enterprise between the middle of next week and the end of the week
after that (depends a bit on internal QA and feedback from the community).
regards,
Thomas
parent reply other threads:[~2024-01-12 15:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.411.1705063250.335.pve-devel@lists.proxmox.com>]
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=678491c0-6ddb-4478-83ed-7ebc156a99c0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=mark@tuxis.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox