From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] QA: package.mask policies
Date: Sun, 08 Nov 2009 15:41:08 +0300 [thread overview]
Message-ID: <1257684068.8341.1349.camel@tablet> (raw)
In-Reply-To: <200911071824.16651.scarabeus@gentoo.org>
В Сбт, 07/11/2009 в 18:24 +0100, Tomáš Chvátal пишет:
> * Masking beta...
> This masks are good if the software release is KNOWN to break previous
> behaviour or degrade user experience. Otherwise the software should not be
> masked (its TESTING for purpose, not stable).
God no! If we'll start to do this way we'll loose a way to test packages
that are supposed to go stable. It was told many times that testing
branch is for testing ebuilds, not for packages and if upstream
conciders them beta mask them. Or do you want Gentoo to have upstream
suggested _only for testers_ versions end in stable tree?
> Also the maintainer should watch if the testing branch is still relevant (why
> on earth we have masked 4.0.3_p20070403 version of screen when newer 4.3 is
> stable ;]) and remove the branch+mask when needed.
Yup, such things happen, but this does not mean we should stop using
package.mask for beta software.
--
Peter.
next prev parent reply other threads:[~2009-11-08 12:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 17:24 [gentoo-dev] QA: package.mask policies Tomáš Chvátal
2009-11-07 18:03 ` William Hubbs
2009-11-07 18:33 ` [gentoo-dev] " Christian Faulhammer
2009-11-07 18:56 ` William Hubbs
2009-11-07 19:03 ` Duncan
2009-11-08 0:08 ` Nirbheek Chauhan
2009-11-08 1:25 ` Duncan
2009-11-08 23:46 ` Vlastimil Babka
2009-11-08 1:26 ` Kent Fredric
2009-11-08 15:13 ` Christian Faulhammer
2009-11-09 13:17 ` Duncan
2009-11-08 12:41 ` Peter Volkov [this message]
2009-11-08 16:57 ` [gentoo-dev] " Jeroen Roovers
2009-11-08 17:20 ` Tomáš Chvátal
2009-11-11 16:43 ` Jeroen Roovers
2009-11-11 17:11 ` [gentoo-dev] " Torsten Veller
2009-11-11 21:54 ` Jeroen Roovers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1257684068.8341.1349.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox