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

Test the branding migration with multi account #3515

Closed
ogoffart opened this issue Jul 29, 2015 · 9 comments
Closed

Test the branding migration with multi account #3515

ogoffart opened this issue Jul 29, 2015 · 9 comments
Assignees
@dragotin
Labels
ReadyToTest QA, please validate the fix/enhancement
Milestone
2.0 - Multi-account

Comments

@ogoffart
Copy link
Contributor

accountmigrator.cpp do the migration from normal owncloud to the branded client. It has not been tested with 2.0 yet. We need to make sure it still work, or fix it, or get rid of the feature.
@ogoffart ogoffart mentioned this issue Jul 29, 2015
Closed
16 tasks
@guruz guruz added this to the 2.0 - Multi-account milestone Jul 30, 2015
@dragotin
Copy link
Contributor

I think we should try to keep it, it is useful if a branded version is rolled out but users had unbranded clients before.

@dragotin dragotin assigned ogoffart and unassigned dragotin Jul 31, 2015
@ogoffart ogoffart assigned dragotin and unassigned ogoffart Aug 6, 2015
@ogoffart ogoffart added the ReadyToTest QA, please validate the fix/enhancement label Aug 6, 2015
@Dianafg76
Copy link

@ogoffart What are the steps to reproduce this?, Thanks

@ogoffart
Copy link
Contributor Author

ogoffart commented Aug 7, 2015

I don't really know. It has something to do with installing some version of the cummunity client, then some version of the branding client and it should go and read the config of the community client and if the URL is the same it should import the account.

@dragotin must know what is the exact devliverable of the feature.

@guruz
Copy link
Contributor

guruz commented Aug 17, 2015

I think this was done once for @moscicki ?

@dragotin
Copy link
Contributor

The feature is still missing in 2.0.0 - so nothing to test so far.

We're investigating if we still need it in 2.0.0

@rperezb
Copy link

rperezb commented Aug 21, 2015

If this were needed, please ping.
In the meantime, @davitol is going to check the upgrade of branded clients, from 1.8.4 to 2.0.0 with multiaccount enable and without it.

@dragotin
Copy link
Contributor

There is no branding migration in 2.0.0 as @MTRichards agreed on.

@MTRichards
Copy link

right, no auto migration - but you should have to upgrade.

@davitol
Copy link

davitol commented Aug 21, 2015

Upgrade 1.8.4 (single-account) ➡️ 2.0.0 (single-account) ✅
Upgrade 1.8.4 (single-account) ➡️ 2.0.0 (Multi-account) ✅

ogoffart added a commit that referenced this issue Sep 1, 2015
@ogoffart
Remove the accountmigrator.cpp It is not used
0fa4353 
This was used to convert the config from the community client to
the  branded client. But we don't need this feature anymore
#3515 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dragotin dragotin

Labels
ReadyToTest QA, please validate the fix/enhancement
Projects
None yet
Milestone
2.0 - Multi-account
Development

No branches or pull requests
7 participants
@ogoffart @guruz @dragotin @MTRichards @rperezb @davitol @Dianafg76