Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs/packaging: Fix formatting issue in package-inclusion.md #501

Merged
merged 1 commit into from
Mar 1, 2024
Merged

docs/packaging: Fix formatting issue in package-inclusion.md #501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/packaging/procedures/package-inclusion.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ This policy sets forth the criteria for a package to be accepted for inclusion i
- DOA (dead-on-arrival) packages are generally rejected from Solus. However, they may be included at the discretion of the project, if they provide unique functionality.
- Projects with no tags/tarballs which lack traction, may be frozen until a suitable release is made. Tagging releases is an indicator for good release engineering practices.
- Typically, we prefer **stable** tagged releases. However, this may be waived if:
- The software has significant traction (i.e. prerelease)
- A bug fix only exists beyond the latest stable release for a git source
- The software has significant traction (i.e. prerelease)
- A bug fix only exists beyond the latest stable release for a git source

### Stack Complexity

Expand Down