migrate existing codereview to the new one
(empty description)
Activity
added type::performance + 1 deleted label
Howto backup data: https://cloud.google.com/appengine/docs/adminconsole/datastoreadmin#backing_up_data
Maybe this guide is better: http://www-cs-students.stanford.edu/~silver/gae.html
Here is my progress. I am able to:
1. Setup a codereview (on django) with roundup (done)
2. Fetch the data from Google Cloud datastore (todo: 'content' and 'patchset' entities)
3. Load the data into the local codereview (using Python scripts):
- codereview_issue, codereview_message and codereview_patch tables: done
- codereview_content, codereview_patchset and codereview_comment tables: in progress
Last, matching users in the roundup table _user (current users of bugs.tryton.org) and the codereview users (current users of codereview.tryton.org) will be needed.On 03 Dec 02:29, Pierre-Louis Bonicoli wrote:
> Here is my progress. I am able to:
> 1. Setup a codereview (on django) with roundup (done)
Are the features the same?
For example, the email notification and reply.
> 2. Fetch the data from Google Cloud datastore (todo: 'content' and 'patchset' entities)
> 3. Load the data into the local codereview (using Python scripts):
> - codereview_issue, codereview_message and codereview_patch tables: done
> - codereview_content, codereview_patchset and codereview_comment tables: in progress
>
> Last, matching users in the roundup table _user (current users of bugs.tryton.org) and the codereview users (current users of codereview.tryton.org) will be needed.
I think this could be done in a second step if it is too much complicate
for now.This can help for migration: https://groups.google.com/d/topic/codereview-discuss/sXZCZNxaHn4/discussion
On #2178 (closed), msg38944 may lead to a migration and also we have now a paid account which remove the initial performance issue so I propose to close this one.
