From c7a074aabfd3f6ae585ed2225baf253b41d38db7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Piotr=20W=C3=B3jcik?= Date: Tue, 9 Mar 2021 20:27:33 +0100 Subject: [PATCH] Manual.md: document requirement of tagged release in place linked from PR template --- CONTRIBUTING.md | 2 -- Manual.md | 5 +++++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d6a7299f64b..4cadfc6265b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,8 +14,6 @@ to build package files from templates. For this guide, we assume you have basic knowledge about [git](http://git-scm.org), as well as a [GitHub Account](http://github.com). -Please note that we do not accept any packages containing non-release versions, such as specific git- or svn-revisions anymore. - To get started, [fork](https://help.github.com/articles/fork-a-repo) the void-linux `void-packages` git repository on GitHub and clone it: $ git clone git@github.com:/void-packages.git diff --git a/Manual.md b/Manual.md index ddb9bec934c..ab86fc39696 100644 --- a/Manual.md +++ b/Manual.md @@ -146,6 +146,11 @@ fonts). Browser forks, including those based on Chromium and Firefox, are generally not accepted. Such forks require heavy patching, maintenance and hours of build time. +Software need to be used in version announced by authors as ready to use by +the general public - usually called releases. Betas, arbitrary VCS revisions, +templates using tip of development branch taken at build time and releases +created by the package maintainer won't be accepted. + ### Package build phases