postponed: Moreblocks discussion issue 1.2.1 #7003

Open
opened 2024-06-27 07:31:16 +00:00 by AliasAlreadyTaken · 1 comment

This is the moreblocks milestone. This milestone deals with nothing but the addition of flux' flavour of moreblocks: https://github.com/fluxionary/minetest-moreblocks

From the comment in #2915 (comment) :

Let's gather what needs to be done to adopt the fork

  • Database needs to have a modification_date: your-land/bugtracker#4526
  • Deal with Worldedit saves, old backups and anything that might break between versions
  • Upgrade all database blocks to latest version, so we can traverse them with a script
  • Split the fork into smaller parts so that upstream has a chance to review them
  • Tell Alias to stop being a coward! :D
  • Extensive testing
  • minetest. conf: stairsplus.in_creative_inventory = false
  • minetest. conf: stairsplus.crafting_schemata_enabled = false
This is the moreblocks milestone. This milestone deals with nothing but the addition of flux' flavour of moreblocks: https://github.com/fluxionary/minetest-moreblocks From the comment in https://gitea.your-land.de/your-land/bugtracker/issues/2915#issuecomment-77728 : Let's gather what needs to be done to adopt the fork * [ ] Database needs to have a modification_date: your-land/bugtracker#4526 * [ ] Deal with Worldedit saves, old backups and anything that might break between versions * [ ] Upgrade all database blocks to latest version, so we can traverse them with a script * [ ] Split the fork into smaller parts so that upstream has a chance to review them * [x] Tell Alias to stop being a coward! :D * [ ] Extensive testing * [ ] minetest. conf: `stairsplus.in_creative_inventory = false` * [ ] minetest. conf: `stairsplus.crafting_schemata_enabled = false`
AliasAlreadyTaken pinned this 2024-07-02 11:55:19 +00:00
AliasAlreadyTaken added this to the moreblocks milestone 2024-07-02 11:55:46 +00:00
AliasAlreadyTaken added the
1. kind/other
label 2024-07-02 11:55:51 +00:00
Author
Owner

What's important here and why I hesitated so long is that there is no way back. Once the LBM converted all the blocks to the new version, this mapblock cannot go back to old moreblocks. Should anything happen and we need to rollback, it's a question whether to restore from backup or manually or via some "reverse script". Such a script does not yet exist.

In the very worst case, if the conversion script flux made doesn't work or is not available and when a worldedit schematic needs to be imported, we can spin up a server with the old moreblocks, import the schematic, upgrade, export the schematic and then import to main. Means, there is an "onboard" way to do it, albeit inconvenient.

In the bugtracker of moreblocks, I cannot see anything that would prevent us. A bug is fixed with 5.9.0, which at the time of writing is on hold regarding the delivery, but that should not prevent us from delivering either.

What's important here and why I hesitated so long is that there is no way back. Once the LBM converted all the blocks to the new version, this mapblock cannot go back to old moreblocks. Should anything happen and we need to rollback, it's a question whether to restore from backup or manually or via some "reverse script". Such a script does not yet exist. In the very worst case, if the conversion script flux made doesn't work or is not available and when a worldedit schematic needs to be imported, we can spin up a server with the old moreblocks, import the schematic, upgrade, export the schematic and then import to main. Means, there is an "onboard" way to do it, albeit inconvenient. In the bugtracker of moreblocks, I cannot see anything that would prevent us. A bug is fixed with 5.9.0, which at the time of writing is on hold regarding the delivery, but that should not prevent us from delivering either.
AliasAlreadyTaken changed title from 1.1.126 to postponed: Moreblocks discussion issue 1.2.1 2024-10-31 10:01:25 +00:00
AliasAlreadyTaken unpinned this 2024-11-06 14:30:22 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#7003
No description provided.