The module currently doesn't have an upgrade path. It will need one for the 1.0 release and I'd like to see the upgrade path tested through a few beta releases.

CommentFileSizeAuthor
#5 upgrade-path-1528930.patch721 bytesstefank

Comments

jim0203’s picture

jim0203 commented
Issue tags: +Release-blocker

Tagging

stefank’s picture

stefank commented
Version: 6.x-1.0-alpha5 » 7.x-1.0-beta2
Issue summary: View changes
stefank’s picture

stefank commented
Version: 7.x-1.0-beta2 » 7.x-1.x-dev
stefank’s picture

stefank commented

@jim0203 Can you explain here. We not making any changes to db, we are just moving variables over. Do we actually need an upgrade path? shouldnt that be a manual one, what we can explain in README.txt.
Thanks

stefank’s picture

stefank commented
Status: Active » Needs review
StatusFileSize
new upgrade-path-1528930.patch721 bytes

Ok, here is a patch to test.

jim0203’s picture

jim0203 commented

Hi @stefank! Firstly, thanks for all your work in the issue queue, and apologies for going AWOL. I've been very busy with my PhD but would like to get a D8 version of the module released (if there is sufficient demand), and that means getting the issue queue cleared for the D7 version of the module.

With regards to your question, I'm a bit rusty on what the upgrade process from D6 to D7 involves, in terms of modules. From the outset I've been very keen that CSM is as easy to use as possible, so if we can simplify things by building in an upgrade path rather than directing the user to a README then I'd like to go down that route.

I'll have a look at your patch (and at your other patches elsewhere in the issue queue) soon. Thank you again!