-
Notifications
You must be signed in to change notification settings - Fork 9
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
Release API changes to RWB staging environment #1600
Comments
@vinayvenu the code changes done for #1579 are present in 7.3 branch and are extensive, which cause problems with cherry picking into 6.1 branch. Therefore, i informed Maha that it would make sense for us to go ahead with 7.3 server release on RWB with few other things cherry picked than do it using 6.1 branch. Putting this on hold for now. |
@mahalakshme Starting from this card onwards, we should include a checkitem in the AC, to ensure that we merge RWB Release branch changes to Master or next upcoming release as part of RWB Prod Deployment cards. This would ensure we do not leave out any hot-fixes made for RWB from not being applied on Avni or Later releases of RWB. |
Releasing with tag v7.3.1 |
Deployed following to RWB Staging Env with tag v7.3.1 :
|
|
@AchalaBelokar from the org, i see that you have 3 different LocationTypes with the same LevelNumber value(1), as seen in this screenshot, which is causing this issue. Please check for org which has a single LocationType in the heirarchy for Dam/Nalla. |
- Before doing the above, merge the latest 6.1.x version to 7.x since we have released some changes later
- Issues in retrieving approval status avni-server#723
- locations should not need lastModifiedDateTime to be mentioned avni-server#726
The text was updated successfully, but these errors were encountered: