Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Make sure a site can be succesfully moved to another platform (ie: release), To ensure that the site can successfully run on it's destination platform. Also pick up if a db update is required.
We don't have to do this immediately, as we can roll back on issues, but without this functionality we are operating with much less of a safety net.
Comment | File | Size | Author |
---|---|---|---|
#9 | Picture 19.png | 83.66 KB | adrian |
#8 | Picture 17.png | 94.72 KB | adrian |
#7 | Possible upgrades | 91.24 KB | adrian |
#7 | No possible upgrades | 91.32 KB | adrian |
#6 | Picture 10.png | 57.62 KB | adrian |
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedThis belongs to hosting.
Comment #2
anarcat CreditAttribution: anarcat commentedWe should probably do this for 0.2.
Comment #3
anarcat CreditAttribution: anarcat commentedI think this works now. We can't downgrade drupals. Not sure all is done, maybe adrian can comment on that.
Comment #4
adrian CreditAttribution: adrian commentedNot there yet.
http://drupal.org/node/368294 is a pre-requisite for this, and i'm almost done with it.
Comment #5
adrian CreditAttribution: adrian commentedThe requirements are now basically done.
What needs to happen now is we need to test the packages associated between the platforms.
ie: Select the packages between the two target platforms and compare them.
Comment #6
adrian CreditAttribution: adrian commentedYay. getting there
Comment #7
adrian CreditAttribution: adrian commentedCommitting what i have so far.
I realized the only way to do this was to provide the user with the relevant details so they could make up their own mind.
I still need to do the form plumbing.
You need to run update.php, and this will create new verify tasks for _EVERYTHING_.
This can take a long while.
We have some cleaning up to do of this from a UX standpoint too.
On the provision side, the backend should do some checking from the package manifests during validate as well.
Comment #8
adrian CreditAttribution: adrian commentedAdded form elements and made the form validate.
sadly, migrate seems broken on the provision side now =\
This screen also needs a bit of css love.
Comment #9
adrian CreditAttribution: adrian commentedAnd this is what it looks like.
I'm stopping here.
We can create new tickets for any issues we find, and i'm sure there will be several.
Comment #10
adrian CreditAttribution: adrian commented