@jinmuluo I rarely consider that question, so I had to think through how to find that information. Here's what I discovered:
- In one of the latest ctsm5.3 tags I searched through the /doc/ChangeLog file. In the vicinity of tag ctsm5.2.005 I searched for "cesm" and found that the cesm5.2.006 tag updated externals to cesm2_3_beta17, which suggests preparations for a new cesm tag.
- Two ctsm tags later I found "Tag name: tmp-240620.n01.ctsm5.2.007" and an explanation that we were waiting for the completion of a new cesm tag.
- I interpret this to mean that cesm2_3_beta17 likely includes ctsm5.2.007. That's probably the closest to ctsm5.2.005 that you will get. A complication for you, though NOT insurmountable, is that ctsm5.2.007 replaced "checkout_externals" with "git-fleximod" so after checking out cesm2_3_beta17 I would NOT just replace ctsm5.2.007 with 005. Instead I think you may find that your changes in 005 do not conflict with the changes from 005 to 007. If so, you should bring your work to 007 manually (possibly by just copying the relevant files but make sure you don't miss differences in your files from 005 to 007).
- In this version you cannot use ./manage_externals/checkout_externals. Instead type "./bin/git-fleximod update" and "./bin/git-fleximod --help"