-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade to Tripal 2.1 #1
Comments
Ethy do you want me to migrate the JIRA issue over using the importer I used for GCV issues? There's a lot of extra detail in the JIRA comments that would be brought over that way. I was a bit confused by the description of status above since the work done so far in the sandbox has not done any of the chado upgrading, which I think will be the sticky part (as discussed in the JIRA comments). Alternatively we could start fresh here and just refer back to LEGUME-710 in JIRA as needed. |
Malachy and I talked about the upgrade process on Monday. He suggested doing the Tripal 2.1 upgrade first, releasing it after careful testing , then doing the Chado 1.3.1 upgrade. So I split LEGUME-710 into two issues. I also tried to consolidate the comments into the description, in hopes that what has been done and what needs to be done could be more clear. If I've left stuff out or stated things incorrectly, it might be best to edit the description rather than add a comment (if possible), in hopes of limiting the time it takes to parse the issues. The comments will stack up soon enough....
I didn't presume to suggest the same order of operation for LIS, but you could add that to the descriptions, or make separate issues, if it makes sense to you.
Ethy
…________________________________
From: adf-ncgr <[email protected]>
Sent: Thursday, October 19, 2017 4:23 PM
To: LegumeFederation/tripal
Cc: Cannon, Ethalinda K [COM S]; Assign
Subject: Re: [LegumeFederation/tripal] Upgrade to Tripal 2.1 (#1)
Ethy do you want me to migrate the JIRA issue over using the importer I used for GCV issues? There's a lot of extra detail in the JIRA comments that would be brought over that way. I was a bit confused by the description of status above since the work done so far in the sandbox has not done any of the chado upgrading, which I think will be the sticky part (as discussed in the JIRA comments). Alternatively we could start fresh here and just refer back to LEGUME-710 in JIRA as needed.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADQEoVLDC8GzwABPoAcOs4FrZEsvgX7yks5st73QgaJpZM4P_3jS>.
|
OK, sounds good. I hadn't seen #2 when I made my first comment, so I'm slightly less confused now. thanks |
Start with PeanutBase since it has less data to contend with, test, then release for month for further testing.
Instructions at: http://tripal.info/tutorials/v2.x/upgrade_2.0_to_2.1
Previous work on this issue was done with LIS, in the sandbox lis-chado-update, and appears to have been successful, though not thoroughly tested.
The follow steps were done on the sandbox above:
The text was updated successfully, but these errors were encountered: