Open johanvdw opened 3 days ago
steps to migrate the db:
# mail saw no changes, so not needed to fake
python -m pretalx migrate person 0027 --fake
python -m pretalx migrate devroom_settings 0007 --fake
after updating the branch:
python -m pretalx migrate person 0030 --fake
python -m pretalx migrate devroom_settings 0011 --fake
python -m pretalx migrate submission 0078 --fake
As we found out, forking is harder than merging, but let's try to track either pretalx v2024.3.1 or main and rebase our changes. I'm creating this issue to follow up and creating new branches in pretalx-integration and pretalx.
model changes required :
strictly required changes before we move:
other changes that should happen, but are not yet needed at this point
nice to have, but may have better solutions:
this overview was created by running
git diff fosdem_2024_extra..fosdem_2024_rebase
which should help find the changes mentioned above