Splitting out from #2699397: Release 7.x-2.2 → ...
Currently the only way that we have of testing upgrades (especially major upgrades such as 1.x - 2.x) is to manually create nodes on the old version, manually update, then check. All manual.
It would be easier for us to develop if there was something more automated, so that we can test more frequently and catch edge cases or regressions.
This issue is to discuss how to do this...
Closed: outdated
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
All feature request against 7.x would be closed. The focus is now on Drupal 10 release. If you feel this issue is relevant for Drupal 10 version of the project, please feel free to re-open and update the issue. Thanks for the discussion/contribution.
You may follow 📌 Port PM to Drupal 10 Active to know more about Drupal 10 status.