-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
TRUNK-4730 Verify that all relevant domain objects have changed_by and date_changed fields #1880
Conversation
@manuela-grindei, thanks for your PR! By analyzing the history of the files in this pull request, we identified @bmamlin, @WolfSchlegel and @ivange94 to be potential reviewers. |
@manuela-grindei thanks again for working on this! 👍 |
<changeSet id="TRUNK-4730-20161114-1000" author="grindei" dbms="mysql"> | ||
<preConditions onFail="MARK_RAN"> | ||
<not> | ||
<columnExists tableName="concept_class" columnName="date_changed"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the fix version is 2.1, can you move these changesets to liquibase-update-to-2.1.xml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done 👍
Fixed integration test failures. |
@manuela-grindei can you squash these commits into one as advised at https://wiki.openmrs.org/display/docs/Pull+Request+Tips |
… and liquibase patches
78a6ad6
to
338f1f2
Compare
Squashed commits |
@@ -83,7 +83,6 @@ public void addAttribute(A attribute) { | |||
if (getAttributes() == null) { | |||
setAttributes(new LinkedHashSet<A>()); | |||
} | |||
// TODO validate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these three TODO removals also part of this ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to squash everything, including a merge of upstream master, which gave those TODO removals.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There used to be 3 commits, one of which was a master upstream merge
subscription.maxElementsInMemory=500 | ||
subscription.eternal=false | ||
subscription.timeToIdleSeconds=300 | ||
subscription.timeToLiveSeconds=300 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this file also part of this ticket?
* v. 2.0. If a copy of the MPL was not distributed with this file, You can | ||
* obtain one at http://mozilla.org/MPL/2.0/. OpenMRS is also distributed under | ||
* the terms of the Healthcare Disclaimer located at http://openmrs.org/license. | ||
* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this part of this ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this comes from the upstream merge
@manuela-grindei i see so many changes that have nothing to do with this ticket. Can you fix that? |
I'm afraid I don't know how... |
Did you get a chance to read this https://wiki.openmrs.org/display/docs/Pull+Request+Tips and https://wiki.openmrs.org/display/docs/Pull+Request+Tips |
Absolutely, I read it |
As a last resort, if you do not find it easy to separate your changes from other commits that have already been merged, you may just create a new branch and put back your changes one by one before making a new pull request. |
This looks very strange, I think I will need to delete the repo again and recreate everything using patches... However, we need to merge quickly next time, so that we do not need to squash anything again. Please let me know if you are fine with the actual changes, as we need the final version in the next PR to be able to quickly merge it into master. We could choose a time of very low activity in the repo, maybe during Christmas, to prevent upstream master changes from happening. |
@manuela-grindei there will always be a possibility of commits before your pull request is merged. Even if a pull request is open and reviewed in 30 minutes, there will always be a chance of commits that happen within for instance 15 minutes before the merging. This is the nature of distributed development. :) |
You're totally right in what you say. |
In the meantime, I can provide a patch with the changes to you or someone else who can squash without issues, so we can still finish the story and merge the code in the repo. |
@manuela-grindei if you fail to get it right, you can post on talk, detailing the exact steps or commands you executed and the results. Then you will get answers from other contributors who have been there before. For i have seem many of them successfully squash their commits. So be sure that you will get help from others' experiences! :) |
@manuela-grindei my advice is that you do not miss out on the chance to learn this. As long as you plan to have a software development career, there are things you will have no option but patiently learn, regardless of the project you will chose to work on! :) |
Description
Added new attributes to classes, added new mappings to Hibernate files, added corresponding Liquibase patches
Related Issue
see https://issues.openmrs.org/browse/TRUNK-4730
Checklist:
git pull --rebase upstream master
.mvn clean package
right before creating this pull request andadded all formatting changes to my commit.