Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note to check liquibase command run correctly #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ziqing26
Copy link
Contributor

Outline of Solution

  • Add a note on how PM can check if a liquibase tag is added correctly.
  • Change the instructions from bullet to numbering points for easier reference.

Copy link

@cedricongjh cedricongjh left a comment

Choose a reason for hiding this comment

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

LGTM! thanks for updating the docs

Copy link
Contributor

@NicolasCwy NicolasCwy left a comment

Choose a reason for hiding this comment

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

LGTM! Just one nit from a previous PR which we can correct here too

@@ -104,7 +104,8 @@ New releases are made every set period of time (typically every week), in which
* Before release day:
* [Create an issue for the release](https://github.com/TEAMMATES/teammates/issues/new?template=release.md) to announce the scheduled release time.
* Update the "about page" with the names of new contributors, if any.
* Check if any schema change is needed for this release. If so, inform PM that this release requires maintainance mode and generate Liquibase changelog (refer to [Schema Migration](#schema-migration)).
* Check if any schema change is needed for this release. If so, generate Liquibase changelog (refer to [Schema Migration](#schema-migration)) and inform PM that this release requires maintainance mode.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is maintenance mode needed? I thought that prod should never go down for schema changes, we could correct this here

Copy link

Choose a reason for hiding this comment

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

Hopefully, most schema changes are backward compatible (i.e., no need to go into maintenance mode) but some might not be. So, should cover both cases in the docs.

Copy link
Member

Choose a reason for hiding this comment

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

@damithc schema changes + data migration in SQL is no different than that in Datastore. There is no need for any additional concern.

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.

5 participants