We're preparing to upgrade a heavily customized platform from Group 1.x to 2.x and found the existing upgrade docs could use some updating. I ended up doing a fairly substantial rewrite rather than piecemeal edits, so I wanted to get community feedback before touching the docs page directly.

The proposed revision is here: https://gist.github.com/scottatdrake/cbdaf04d9a151e748afd277d3f4fe73f

The main thing I tried to do was make the 2.x vs 3.x boundary really explicit (what to rename now and what to leave alone. I also updated the flexible_permissions guidance to reflect its integration into core 10.3 as the Access Policy API, and added detailed method migration tables for GroupContentEnablerBase and GroupRelationTypeManager.

I would appreciate a sanity check and reassurance that making these edits would be welcome and helpful to others. My updated version is much more verbose but hopefully also more complete.

Comments

scottatdrake created an issue. See original summary.

richarddavies’s picture

richarddavies commented

I took a quick look at your proposed changes. It's been a while since I did our v2->v3 migration, and even longer since I did our v1->v2 migration, so I'm not able to give it a detailed technical review, but generally it looks good to me. It's very thorough and detailed, and looks to be a good improvement over the current documentation. I believe this document would have made my v1->v2 migration easier. Nice job and thanks for working on this.

scottatdrake’s picture

scottatdrake commented
Assigned: Unassigned » scottatdrake
Status: Active » Fixed

I went ahead and updated the documentation at: https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib...

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.