Skip to content

ROADMAP.md

Latest commit

 

History

History
86 lines (58 loc) · 2.26 KB

ROADMAP.md

File metadata and controls

86 lines (58 loc) · 2.26 KB
Raw

Roadmap

Public Roadmap is managed through GitHub Projects.

This file describes how the v2RayTun public roadmap is organized.

Purpose

The roadmap is used to track:

  • Planned features
  • Platform-specific development
  • Known limitations
  • Feature requests
  • Declined ideas
  • Release-related work

Platforms

Roadmap items may be assigned to one or more platforms:

  • Android / Android TV
  • iOS
  • macOS
  • Windows
  • Linux

Some features may be platform-specific because each platform has different UI, system integration, release rules, and technical limitations.

Roadmap statuses

Roadmap items may use the following statuses:

Status Meaning
Needs review New item that has not been reviewed yet
Accepted The idea or issue is valid, but not scheduled yet
Planned The item is planned for development
In progress Work has started
Done The item has been completed or released
Declined The item is not planned for implementation

Declined items

Declined items may remain visible when possible.

This helps users understand which ideas were reviewed and why they are not currently planned.

Common reasons for declining an item may include:

  • The request does not match the current product direction
  • The feature would be too difficult to maintain
  • The platform does not support the required behavior
  • The feature has security, privacy, or compatibility concerns
  • There is already an alternative solution

Feature requests

Feature requests should be submitted through GitHub Issues using the feature request template.

A good feature request should include:

  • Target platform
  • Problem description
  • Expected behavior
  • Use case
  • Possible alternatives, if any

Bug reports

Bug reports should be submitted through GitHub Issues using the bug report template.

A good bug report should include:

  • Platform
  • App version
  • Operating system version (including device model or vendor UI version if applicable)
  • Where the app was installed from
  • Steps to reproduce the problem
  • Logs or screenshots, if available

Releases

Completed roadmap items may be linked to GitHub Releases when applicable.

See RELEASES.md for release channels, versioning, and release asset naming.