It might be a good idea to keep D9 info, as D9 is quite a handy in-between step coming from D7, as D9 supports PHP 7.4 and 8.X at the same time.
This is enabling users to switch PHP versions back and forth until extension compatibility for PHP 8.1 is given to update to D10
@resga@jofranz - I'm curious: are there really any differences in the instructions for D9/D10? In test-infra, the build-scripts are basically identical:
(The only difference there is that the D10 adds composer-based version of drush, which isn't really a Civi-installation step. And, of course, the version-constraint is different, ^9 vs ^10.)
(Note: The test-infra uses some helper functions to share code between the builds - eg composer_allow_common_plugins, civicrm_download_composer_d8, civicrm_install_cv. But after skimming the current code, it looks like they run the same way for D9/D10. )
Actually, maybe the question ^^ should be directed to @jackrabbithanna@DaveD. Do you all know of any differences in current install process for Civi on D9-vs-D10? (I don't...)
DaveD is correct, no changes except versions and PHP version. For drush, we've been keeping https://drupal.org/project/civicrm_drush working. Use Drush 11 for now, we need to tweak it for Drush 12.
It might be a good idea to keep D9 info, as D9 is quite a handy in-between step coming from D7, as D9 supports PHP 7.4 and 8.X at the same time.
Just dropping in here to suggest that even if it's useful to have any D9-specific steps somewhere, I think it would be much better moved to some kind of appendix or so. To my mind having the D7/D9/D10 on that page seems very confusing for new folks.
Happy to make a PR if there's no strong opposition to this?