-
Notifications
You must be signed in to change notification settings - Fork 521
Conversation
@ktdreyer I wonder if removing everything might be a bit too "aggressive" for now. Shouldn't we just update the |
The files will still be in the Git history. Removing the files makes it clear to users and contributors that developers are focused on the new area. |
Why not just archive the repo so it's readonly? And how will they know where to find new development if the readme is even empty? |
Correct. Although I still think that removing everything is a bit aggressive, I would at least leave a comment in README.md to let users know what's happening. |
Whoops, sorry! I wrote a new README but I forgot to push it in this PR. I've amended and re-pushed. It can be a little difficult to read in this large GitHub diff, so I'll paste the README contents here:
|
Remove all the files in the repository and point users at the new Containerfile location. Signed-off-by: Ken Dreyer <[email protected]>
@dmick , is this ready to merge now? |
These jobs are no longer needed, see ceph/ceph-container#2256 Signed-off-by: Guillaume Abrioux <[email protected]>
We should disable/delete the Jenkins jobs that use it first, probably.
Working on that and the change to the third release "ceph" job to add the
new container build
…On Mon, Dec 9, 2024, 7:12 AM Ken Dreyer ***@***.***> wrote:
@dmick <https://github.com/dmick> , is this ready to merge now?
—
Reply to this email directly, view it on GitHub
<#2256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJYENEDTGVSS7H7APRG3D2EWXPLAVCNFSM6AAAAABS6JYKZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRYGI4DSNBSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Now that ceph/ceph-build#2305 is done, @dmick is this read to merge? |
I think so. I think ceph/ceph#60936 is too if I could get a review 😄 |
Remove all the files in the repository and point users at the new
Containerfile
location.