| This is more the sentiment that I was hoping to convey. Sure, I have my finger on the pulse of the mailing list and the packages coming down the pipe, but assuming that everyone does and/or will is not a safe assumption. At the minimum, publishing the versioned repos at $repourl/debian-16.2.14 but not cutting the symlink over for $repourl/debian-pacific until “ready” seems like a very easy and useful release process improvement to prevent these specific issues going forward. Likewise, $repourl/rpm-pacific is already pointing to $repourl/rpm-16.2.14 as well, so its not a debian specific issue, albeit it looks like there were no issues with missing packages on el8. But the packages were still “pre-released” before we are supposed to use them. Anything making it to $repourl/{deb,rpm}-$named_release should be “safe.” Because the documentation uses the named repos, as it should, and right now the documentation is effectively broken.
Reed
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
