Page Comparison

...

1. A migrator files a ticket in the Kuali Rice JIRA project requesting migration of a data set to the Rice database.
2. Upon approval, the migrator copies the data set to the <Repository Root/tags/<client release version> directory, citing the Kuali Rice JIRA ticket.

   Code Block
   borderStyle solid title Example:Migrating to <tags>
   svn copy https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 -m "<KR JIRA ticket>"

3. Prior to a release, the migrator adds a task (or requests that a task be added) in the Deployment Plan stating that the data set is to be migrated.
4. The Rice Service Manager creates a ticket in the Kuali Rice JIRA project that reflects this task and assigns it to the Rice DBA.
5. The Rice DBA pulls checks the data set down out from the respositoryrepository.

   Code Block
   borderStyle solid title Example:Checking Out Data Set from Repository
   $ svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 or [subversionFiles/dataSets/KualiCoeus/]$ svn update

6. During a dry-run deployment, the Rice DBA executes the data set scripts against the UPSTAGE environment database.
7. At deployment time, the Rice DBA executes the data set scripts against the production database.