Changes between Version 89 and Version 90 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Jan 22, 2015, 8:43:22 PM (8 years ago)
Author:
Beman Dawes
Comment:

Mention option of transfering existing repo.

Legend:

Unmodified
Added
Removed
Modified
  • ReleasePractices/ManagerCheckList

    v89 v90  
    6767The release manager performs two steps to add the new library to [https://github.com/boostorg GitHub]:
    6868
    69     * [https://github.com/orgs/boostorg/new-team Create the library's repository]. Note: the release manager creates a repo that is empty except for a readme file. The library's developer is responsible for creating the library's contents.
     69    * Do one of two things:
     70        * If the library already has a !GitHub repository, [https://help.github.com/articles/transferring-a-repository/ transfer the repository to boostorg]. Getting the maintainer to transfer into the organization is a bit awkward. So it might be best to first transfer the repo to an admin, who can then transfer it into the organization and set up the team.
     71        * If the library does not already have a !GitHub repository, [https://github.com/organizations/boostorg/repositories/new Create the library's repository]. Note: the release manager creates a repository that is empty except for a readme file. The library's developer is responsible for creating the library's contents.
    7072    * [https://github.com/orgs/boostorg/new-team Create a team for the library].
    7173