Update dist and metadata

dist/dist.py

@@ -28,51 +28,48 @@
 
 
 4. run test/warningMultiprocessTest.py for lowest and highest Py version -- fix all warnings!
-4b. run `from music21.test import treeYield
+5. run `from music21.test import treeYield
     and then run `treeYield.find_all_non_hashable_m21objects()` and check that the set returned is
     empty.  Note -- it will print a bunch of module names, but only the final set matters.
     Then do the same for `treeYield.find_all_non_default_instantiation_m21objects()`.
-5. commit and wait for results on GitHub Actions
+6. commit and wait for results on GitHub Actions
      (normally not necessary, because it's slower and mostly duplicates multiprocessTest,
      but should be done before making a release).
 
-6. run documentation/make.py clean  (skip on minor version changes)
-7. run documentation/make.py linkcheck  [*]
-8. run documentation/make.py   [*]
+7. run documentation/make.py clean  (skip on minor version changes)
+8. run documentation/make.py linkcheck  [*]
+9. run documentation/make.py   [*]
 
 [*] you will need sphinx, Jupyter (pip or easy_install), markdown, and pandoc (.dmg) installed
 
-10. ssh to athena.dialup.mit.edu (yes, dialup!), cd music21/doc and rm -rf *  (skip on minor version changes)
+10. move music21 docs to music21.org via Amazon S3 (contact MSAC for authentication if need be)
 
-11. run documentation/upload.py or upload via ssh.
-   -- you will need an MIT username and password + a dual authentication passcode
-
-12. zip up documentation/build/html and get ready to upload/delete it.
+11. zip up documentation/build/html and get ready to upload/delete it.
     Rename to music21.v.7.1.0-docs.zip (skip for Alpha/Beta)
 
-13. Run "hatch build" -- requires hatch to be installed "brew install hatch"
+12. Run "hatch build" -- requires hatch to be installed "brew install hatch"
 
-14. Run this file -- it builds the no-corpus version of music21.
+13. Run this file -- it builds the no-corpus version of music21.
     DO NOT RUN THIS ON A PC -- the Mac .tar.gz might have an incorrect permission if you do.
 
-15. PR and Commit to GitHub at this point w/ commit comment of the new version,
+14. PR and Commit to GitHub at this point w/ commit comment of the new version,
     then don't change anything until the next step is done.
     (.gitignore will avoid uploading the large files created here.)
 
-16. Switch back to master/main branch
+15. Switch back to master/main branch
 
-17. Tag the commit: git tag -a vX.Y.Z -m "music21 vX.Y.Z"
+16. Tag the commit: git tag -a vX.Y.Z -m "music21 vX.Y.Z"
     Don't forget the "v" in the release tag.
     Sanity check that the correct commit was tagged: git log
 
-18. Push tags: git push --tags  (or git push upstream --tags if not on main branch)
+17. Push tags: git push --tags  (or git push upstream --tags if not on main branch)
 
-19. Create a new release on GitHub and upload the TWO non-wheel files created here and docs.
+18. Create a new release on GitHub and upload the TWO non-wheel files created here and docs.
     Drag in this order: .tar.gz, -docs.zip, no-corpus.tar.gz
 
     Finish this before doing the next step, even though it looks like it could be done in parallel.
 
-20. Upload the new file to PyPI with "twine upload music21-7.3.5a2.tar.gz", and same for the
+19. Upload the new file to PyPI with "twine upload music21-7.3.5a2.tar.gz", and same for the
     whl file (but NOT no corpus) [*]
 
     [*] Requires twine to be installed
@@ -87,9 +84,9 @@
         username:your_username
         password:your_password
 
-21. Delete the two .tar.gz files and .whl file in dist.
+20. Delete the two .tar.gz files and .whl file in dist.
 
-22. For starting a new major release create a GitHub branch for the old one.
+21. For starting a new major release create a GitHub branch for the old one.
 
 22. Immediately increment the number in _version.py and run tests on it here
     to prepare for next release.