Closed jdrueckert closed 1 year ago
Workspace lock-file as generated by https://github.com/skaldarnar/node-gooey using
gooey workspace pin --exact
I think all tag creations went through, executed with the following little script:
# in Terasology workspace root with Omega modules and libs checked out locally
echo 'Mark the last commit before the 2023 "Revive" activity
We hope for a more active period for Terasology again, possibly including
drastic cuts of code, major rewrites, and other disruptive activities.
On 2023-07-02, the following repositories were marked with this tag:
- the engine repository MovingBlock/Terasology
- 148 modules of the "Omega lineup" in Terasology/*
- two libraries, MovingBlocks/TeraNUI and MovingBlocks/JNLua' > msg.txt
for repo in . $(find libs/ modules/ -type d -depth 1); do
git -C $repo tag -a pre-2023-revive -F $(pwd)/msg.txt
git -C $repo push origin pre-2023-revive
done
The 148 modules belonging to the Omega distro are taken from https://github.com/Terasology/Index/blob/c6efdcde48fac27f3c2f4573b5d0e945ec5abaf8/distros/omega/gradle.properties.
You can verify
Closed as complete. If we decide that tagging is not sufficient, we can reopen it again with further action items.
Also created a dedicated branch legacy-pre-2023-revive
with the pre-revive state: https://github.com/MovingBlocks/Terasology/tree/legacy-pre-2023-revive
Today I also tagged and branched-off for https://github.com/MovingBlocks/CrashReporter and https://github.com/MovingBlocks/SplashScreen
Motivation
Proposal
Considered Alternatives
Concerns
Task Breakdown
Additional Notes
gooey-node
tool might help with the module tagging