From d2fcbbd287e4b04b449f5a07b1d0fb17773bfab4 Mon Sep 17 00:00:00 2001 From: Joey Riches Date: Fri, 1 Mar 2024 11:47:34 +0000 Subject: [PATCH] docs/packaging: Fix formatting issue in package-inclusion.md --- docs/packaging/procedures/package-inclusion.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/packaging/procedures/package-inclusion.md b/docs/packaging/procedures/package-inclusion.md index 4a23b9eb9..23675c012 100644 --- a/docs/packaging/procedures/package-inclusion.md +++ b/docs/packaging/procedures/package-inclusion.md @@ -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