From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Alexander Zeidler <a.zeidler@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs v3] package repos, software updates: revise Ceph section
Date: Thu, 31 Jul 2025 05:26:57 +0200 [thread overview]
Message-ID: <175393241623.303820.3094203999738059351.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250730180254.320235-1-a.zeidler@proxmox.com>
On Wed, 30 Jul 2025 20:02:51 +0200, Alexander Zeidler wrote:
> - Start by mentioning the preconfigured Ceph repository and what options
> there are for using Ceph (HCI and external cluster)
> - Link to available installation methods (web-based wizard, CLI tool)
> - Describe when and how to upgrade
> - Add new attributes to avoid manual editing multiple lines
> - Create a table as an overview of Ceph release availability,
> maintaining clarity and avoiding duplicated text for each release
> - Advise to read the latest version of the corresponding admin guide
> - Add a TODO describing what to update occasionally
> - List and link to the estimated EOL dates of Ceph releases
> - Revise the descriptions of available repository components
> - Mention when it makes sense to edit a repository file manually
>
> [...]
Applied, thanks!
I commented out the row for tentacle in a follow-up commit for now though, IMO
it can be a tiny bit confusing to have a release listed that's not available
anywhere yet.
[1/1] package repos, software updates: revise Ceph section
commit: 2b32abd4de672abea44b255586d409deb46b760a
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-31 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 18:02 [pve-devel] " Alexander Zeidler
2025-07-31 3:26 ` Thomas Lamprecht [this message]
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=175393241623.303820.3094203999738059351.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.zeidler@proxmox.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.