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.

Sign up for GitHub

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

Jump to bottom

use new registration migration for repositories #11

Merged
merged 7 commits into from
Jul 3, 2015
Merged

use new registration migration for repositories #11

merged 7 commits into from
Jul 3, 2015

Conversation

jreidinger
Copy link
Member

NOTE: for testing only

@lslezak lslezak force-pushed the registration_migration branch 3 times, most recently from abe660a to d10d939 Compare June 18, 2015 20:18
@lslezak lslezak force-pushed the registration_migration branch 3 times, most recently from cade8f1 to 3d36dc4 Compare June 26, 2015 11:18
jreidinger and others added 3 commits July 1, 2015 09:12
@lslezak
aded new migration_proposal.rb client
36b09a0 
- use it instead of the update_proposal which has been designed
  for offline upgrade and does some specific actions not desired in
  online migration

- removed the offline migration workarounds
@jreidinger
Copy link
Member Author

showstopper for me is not using proposal client as base class which would really imporve tests. Also using client only hides that code coverage decrease a lot

@jreidinger
Copy link
Member Author

LGTM, thanks

lslezak added a commit that referenced this pull request Jul 3, 2015
@lslezak
Merge pull request #11 from yast/registration_migration
45239b7 
use new registration migration for repositories
@lslezak lslezak merged commit 45239b7 into master Jul 3, 2015
@lslezak lslezak deleted the registration_migration branch July 3, 2015 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@jreidinger @lslezak