Migration from v1 to v4

[derwaldgeist]

We're currently migrating our Meteor app from Meteor 2 to Meteor 3.

It's been around a while, so it's still using alanning:roles 1.3.0. I saw that you have removed the migration scripts in v4. This is quite a challenge for us, since we would like to do the update of our live system automatically, using quave:migrations.

Is there any opportunity to get these scripts back in Roles v4, or would we really have to update all our live systems gradually and manually, i.e. first from v1 to v3 and then from v3 to v4?

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[jankapunkt]

@derwaldgeist good point. @StorytellerCZ was there a reason to drop the migration scripts? Do you think we should add them back with async compat? Alternatively, could we provide a documentation on how to run them manually using meteor shell?

[derwaldgeist]

Thanks for the feedback. It would be really nice if they were back in the v4 code. The current situation forces me to first update the live systems to v3 and then to v4. I prepared this two-step approach, but I would love to do this in combination, using just a quave:migration update script. For the migration from v1 to v3, this worked perfectly.

[StorytellerCZ]

I would be only for adding them back in case that we say that the current v4 is only for migration purposes and we archive things afterwards.
There were issues with those scripts due to Meteor 3 migration and there were 2 other assumptions: 1. people will migrate one major version at a time to make sure everything works properly, 2. at the time of v4 release everyone who already wanted has already migrated to v3.
As was mentioned in #352 there are also some other issues with missing migration documentation.