This repository was archived by the owner on Jul 28, 2024. It is now read-only.
Labels
Labels
44 labels
- Bugs. For major ones, add "major".
- Pull requests that update a dependency file
- Needs discussion or is being discussed.
- Either a direct duplicate or will be better resolved by another issue
- New feature. See "improvement" for updates of existing functionality.
- Issues related to Gutenberg / block editor in WordPress
- Good issue for community contribution – no need for deep knowledge of VP internals
- Improvement of an existing functionality. See "feature" for new features.
- Can't reproduce, not really a VP issue etc.
- Pull requests that update Javascript code
- Use only for bugs to mark the big ones
- About the project itself – PM (project management), release process, roadmaps, etc.
- DEPRECATED. Use "major" or "noteworthy" for big bugs or changes. No need to mark smaller ones.
- Breaking change between VP versions due to a change in storage format. Needs migration.
- Significant issue or PR, to be highlighted in release notes
- Old issue, no longer relevant.
- Pull requests that update Php code
- Issues related to the main feature of 4.0, plugin support.
- Tracking issue for a release
- DEPRECATED. Blog is not managed via this repo.
- Core VersionPress functionality like tracking actions, creating Git commits, etc.
- Build scripts, IDE settings, CI, Docker dev stack, testing, tooling, etc.
- Markdown documentation, public docs, READMEs
- The 'frontend' React app and other UI things
- DEPRECATED. Since VP 4.0, "plugin support" is the label to use.
- Things like PHP versions, Git versions, supported OS / web servers, etc.
- Testing code. For infrastructure (CI, etc.), use "dev-infrastructure".
- DEPRECATED. Website is not managed via this repo.