Skip to content

Conversation

@doctoryes
Copy link
Contributor

This stage does the following:

  • Includes a data migration to copy the values from old to new field.
  • Changes business logic to switch to using new field.
  • Deletes all code references of the old field.

Please consider the following when opening a pull request:

  • Link to the relevant JIRA ticket(s) and tag any relevant team(s).
  • Squash your changes down into one or more discrete commits.
    In each commit, include description that could help a developer
    several months from now.
  • If running make upgrade, run as close to the time of merging as possible
    to avoid accidentally downgrading someone else's package.
    Put the output of make upgrade in its own separate commit,
    decoupled from other code changes.
  • Aim for comprehensive test coverage, but remember that
    automated testing isn't a substitute for manual verification.
  • Carefully consider naming, code organization, dependencies when adding new code.
    Code that is amenable to refactoring and improvement benefits all platform developers,
    especially given the size and scope of edx-platform.
    Consult existing Architectural Decision Records (ADRs),
    including those concerning the app(s) you are changing and
    those concerning edx-platform as a whole.

@doctoryes doctoryes requested review from a team January 14, 2020 16:00
@doctoryes doctoryes requested a review from a team as a code owner January 14, 2020 16:00
@doctoryes doctoryes requested a review from a team January 14, 2020 16:00
@pwnage101 pwnage101 force-pushed the juliasq/rename_site_configuration_siteconfiguration_values_2 branch 2 times, most recently from 3e65873 to 6d0945c Compare February 21, 2020 22:21
@pwnage101 pwnage101 self-assigned this Feb 21, 2020
@pwnage101
Copy link
Contributor

This is still missing a data migration for the history table, that's coming soon...

@pwnage101 pwnage101 force-pushed the juliasq/rename_site_configuration_siteconfiguration_values_2 branch 2 times, most recently from 61a3ae8 to f8c801c Compare February 24, 2020 19:21
@pwnage101
Copy link
Contributor

jenkins run a11y

@pwnage101 pwnage101 force-pushed the juliasq/rename_site_configuration_siteconfiguration_values_2 branch from f8c801c to b4655da Compare February 25, 2020 17:14
Copy link
Contributor Author

@doctoryes doctoryes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't approve this PR since I opened it 😁 - but 👍

This stage does the following:

- Includes a data migration to copy the values from old to new field.
- Changes business logic to switch to using new field.
- Deletes all code references of the old field.
@pwnage101 pwnage101 force-pushed the juliasq/rename_site_configuration_siteconfiguration_values_2 branch from b4655da to 3541643 Compare February 25, 2020 18:54
@edx-status-bot
Copy link

Your PR has finished running tests. There were no failures.

Copy link
Contributor

@bmedx bmedx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@edx-pipeline-bot
Copy link
Contributor

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

EdX Release Notice: This PR has been deployed to the production environment.

@edx-pipeline-bot
Copy link
Contributor

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

@edx-secure edx-secure deleted the juliasq/rename_site_configuration_siteconfiguration_values_2 branch March 8, 2020 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants