ToneCustoms Development Workflow
This public page documents process, not private roadmaps or protected resource files.
Stages
| Stage | Exit condition |
|---|---|
| Planned | Owner accepts the concept and documents scope |
| Development | Resource implementation underway in its private repository |
| Testing | Build and integrations tested against agreed behavior |
| Needs Fixes | Defect requires correction and another testing pass |
| Verified Working | Owner confirms acceptance criteria in FiveM |
| Released | Owner authorizes customer delivery and release notes |
A GitHub commit, issue status or CI success does not mean a script has been released.
Tracking setup
ToneCustoms keeps protected source, internal issues and unannounced product plans private. The existing private tonyiswavy/tonecustoms_gunjam repository has issue templates and an internal review issue for upcoming work. Its contents are visible only to authorized collaborators.
For an optional consolidated GitHub Projects board under the existing personal account, use New project → Board with columns Planned, Development, Testing, Needs Fixes, Verified Working, Released, and set the project visibility to Private before adding internal issues. Creating a Project board is a separate account-level action; this documentation does not claim one has been created.
New-resource structure
Use the Repository Organization Guide to decide whether a new repository is needed, how to name it, and whether it should be public or private. Use the Resource Repository Checklist when setting up a future private script repository. Follow Release Workflow for testing, delivery and version decisions.
Scope
No automated job in the public documentation repository publishes a FiveM asset or updates Tebex. Script versions and actual customer-facing releases require Tone's approval.