Close release-package acceptance against the Rust-only candidate

Open
  • Is something wrong?
#563 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
godot, linux, macos, python, rust
Domain
build-system, release

Research direction

Start with tools/package/release.py, its release tests and forbidden-content negative controls, then the existing native Linux, Windows and macOS packaging workflow. The issue depends on the Rust-only switch and a palette pause being lifted, and it needs private local ROM inputs. Done means the tests and negative controls pass, each native archive is built, checked and smoke-tested, and the README.txt walkthrough is recorded on a clean Linux environment.

Written by the indexing model from the issue text.

Description

later

Child of https://github.com/TusanHomichi/PSIV/issues/115. Finish only this task in one fresh session and one PR. The parent's original authorization boundaries still apply; this child grants no additional authority. Do not read earlier sessions' transcripts.

Depends on the Rust-only switch and lifting the palette pause. Validate tools/package/release.py and the existing native Linux, Windows and universal macOS workflow; do not rebuild packaging already landed in #247, #276 and #539. Make only scoped acceptance fixes and checklist updates. Verify notices, source/rebuild instructions, forbidden-content guards, player instructions and per-user saves. Preserve the --script save-directory refusal. Use private local ROM inputs only. This PR does not authorize a release tag, publication or distribution of game assets.

Verification: Run release tests and their forbidden-content negative controls; build/check/smoke each native archive. Verify Linux extension and builder require no glibc newer than 2.41. On Linux with an empty user environment and no development tools, follow README.txt through ROM selection, title, ordinary SAVE and fresh-process CONTINUE from another directory. Record revisions, archive identities and platform coverage limits.

If this is too big, publish any progress, split it with proj split FILE (a JSON array of title/body/check tasks), then end the session. Wait for the PR to land before declaring this task done.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
8h 43m
Merged PRs (30d)
288

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TusanHomichi/PSIV

All issues in TusanHomichi/PSIV

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.