Merge branch 'master' into patch-1

Author: Pezi777

user/migrate/open-source-repository-migration.md

@@ -19,20 +19,18 @@ When a repository is migrated, the following information will be transferred to
 * Cron jobs configured for the repository
 * Last build status - the build badge in travis-ci.com will reflect this status until new builds are triggered
 * Next build number
+* Previous build history
 
 ### What information will not be transferred to travis-ci.com?
 
-The following information will not be transferred to travis-ci.com when a repository is migrated.
+The following information will not be transferred to travis-ci.com when a repository is migrated:
 
-* Previous build history - your builds from before the migration to travis-ci.com will remain on travis-ci.org until the  complete build- history migration (sometime in early Q3 2019)
 * Caches - they will be re-created automatically on the first build on travis-ci.com
 
 ## Do I need to make any other changes?
 
 You only need to make any changes yourself if you use any of the following features:
 
-* **build badges**:  make sure to update the URL to reflect the new repository setup in travis-ci.com. In the future, we will automatically redirect travis-ci.org badge URLs to the corresponding travis-ci.com ones.
-
 * **"Protected Branches" feature in GitHub** to require a passing Travis CI build before merging a Pull Request: make sure to edit your required status checks to now use `Travis CI - Pull Request` and/or `Travis CI - Branch`. See: [Required status checks at GitHub](https://help.github.com/articles/about-required-status-checks/).
 
 * **[Travis CLI](https://github.com/travis-ci/travis.rb)**: after migration make sure to add the `--com` flag or [make it your default endpoint](https://github.com/travis-ci/travis.rb#endpoint) by running: `travis endpoint --com --set-default`.
@@ -45,16 +43,15 @@ Your repository on travis-ci.org will be automatically deactivated (that is, it
 
 With this read-only mode:
 
-* All the previous build history will be accessible at travis-ci.org
 * The "Trigger build" functionality won't be available in travis-ci.org
 * It won't be possible to restart a previous job that ran in travis-ci.org
 * The Settings page for your repository will become inactive - the transferred repository settings will now be available in travis-ci.com instead.
 
-In the future, when all the previous build history is migrated, we will provide redirections from all API/web requests going to travis-ci.org to travis-ci.com.
+In the future, we will provide redirections from all API/web requests going from travis-ci.org to travis-ci.com.
 
 ## How long does the migration process take?
 
-The migration process for a repository should not take more than a couple of seconds.
+The migration process for each repository should not take more than a couple of seconds.
 
 ## Can I migrate multiple repositories at once?
 
@@ -77,14 +74,14 @@ If you are already using GitHub Apps for your account in travis-ci.com, you need
 
 3. When activating the Travis CI GitHub App, grant access to the repositories (both public and private) that you want to build in travis-ci.com. Save the changes.
 
-4. Once back in your Travis CI profile, the selected repositories will be listed there. Those projects that were already building in travis-ci.com, or any new public or private projects will now be active in travis-ci.com.
+4. Once back in your Travis CI profile, the selected repositories will be listed there. Those projects that were already building in travis-ci.org will appear in the Migrate tab for your account.
 
 ### The migration steps
 
-1. Once you have granted access via GitHub Apps to the repositories you'd like to build and transfer, a new ["Migrate" tab](https://travis-ci.com/account/migrate) will appear in your account page with a list of the repositories to migrate:
+1. Once you have granted access via GitHub Apps to the repositories you'd like to build and transfer, on the ["Migrate" tab](https://travis-ci.com/account/migrate), there will be a list of the repositories available to migrate:
   ![Migration repository list](/user/images/oss-migration/repos-to-migrate.png)
 
-2. Select the repositories you'd like to migrate and click "Migrate selected repositories",  You'll be asked for a final confirmation - please remember that your build history will not be migrated at this time (See: [What information will not be transferred to travis-ci.com?](#what-information-will-not-be-transferred-to-travis-cicom)).
+2. Select the repositories you'd like to migrate and click "Migrate selected repositories",  You'll be asked for a final confirmation - please remember that you'll need to update protected branches (See: [Do I need to make any other changes?](#do-i-need-to-make-any-other-changes)).
 
 3. Confirm the migration. The icons next to your repository name will show the migration status ("processing", or "migrated"):
   ![Migration statuses](/user/images/oss-migration/migration-statuses.png)