You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  1. Rename GitHub repository
  2. Determine public vs. private API surface in order to get a clear picture on what code elements can be renamed without triggering a breaking change and therefore a major release (if using semantic versioning)
    1. Update source code references
      1. Classes
      2. Interfaces
      3. Imports
      4. Do keep in mind that these have to be separated based on internal vs. published API elements
  3. Update links pointing to the GitHub repository within
    1. source code
    2. documentation that's managed separately from the source code (if applicable)
  4. ReadTheDocs page (if applicable)
  5. Mailing list
  6. Chat rooms (Discord)
  7. Calendar meetings (where applicable)
  8. Wiki pages
  9. Project page update on Hyperledger site
  10. Package managers/published artifacts (where applicable)
    1. npm
    2. Maven/Gradle
    3. Container images
  11. Slide decks (if applicable)
  12. Whitepapers (if applicable)
  13. GitHub Integrations (where applicable):
    1. ZenHub
    2. MergeFreeze
    3. Jira
    4. Gitter
    5. GitGuardian
    6. etc.
  • No labels