public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] stabilizing libraries without testing reverse deps
Date: Sun, 29 Sep 2013 20:03:59 -0700	[thread overview]
Message-ID: <5248EA1F.3030202@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nYf5qMudd5mZQsrs_=_2DcR3q=i4DMxYb4jJAikpR+Zw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

On 9/29/13 7:41 PM, Rich Freeman wrote:
> Even then, we won't get much more than compile testing, or whatever
> test suites the packages happen to come with.

That's right.

I think we can rely on the time packages spend in ~arch to catch the
issues that wouldn't come up with compile and test phases.

Also, when stable is not far behind testing, the testing that ~arch
packages get is more applicable to stable (because there are less
differences). This is one of the main reason for my push to stabilize
more packages (always with proper testing), and I've also seen bugs
being fixed in ~arch but the fixes are not always pushed to stable
(which can be addressed by stabilizing more packages in general).

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  reply	other threads:[~2013-09-30  3:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 21:41 [gentoo-dev] stabilizing libraries without testing reverse deps hasufell
2013-09-29 22:33 ` "Paweł Hajdan, Jr."
2013-09-29 22:40 ` Thomas Kahle
2013-09-30 16:58   ` William Hubbs
2013-09-30 17:12     ` Rich Freeman
2013-09-29 22:54 ` Andreas K. Huettel
2013-09-30  0:14   ` hasufell
2013-09-30  2:41     ` Rich Freeman
2013-09-30  3:03       ` "Paweł Hajdan, Jr." [this message]
2013-09-30  6:14       ` [gentoo-dev] " Agostino Sarubbo
2013-09-30 15:40         ` "Paweł Hajdan, Jr."
2013-10-01 14:13         ` Jeroen Roovers
2013-10-01 16:10           ` "Paweł Hajdan, Jr."
2013-09-30  6:02   ` [gentoo-dev] " Peter Volkov
2013-09-30  6:42 ` Sergey Popov
2013-09-30  7:22 ` Markos Chandras
2013-09-30 10:44   ` hasufell
2013-09-30 11:45     ` Chí-Thanh Christopher Nguyễn
2013-09-30 11:58       ` hasufell
2013-10-01 19:51         ` Peter Stuge
2013-10-01 21:12           ` Kent Fredric
2013-10-02 16:43             ` yac
2013-10-02 17:32               ` hasufell
2013-10-02 18:50               ` Kent Fredric
2013-10-03 16:11             ` "Paweł Hajdan, Jr."
2013-10-03 22:30               ` Kent Fredric
2013-10-04  4:03                 ` "Paweł Hajdan, Jr."
2013-10-04 23:59                   ` Kent Fredric
2013-09-30 16:23       ` Patrick Lauer
2013-10-01 14:27         ` Jeroen Roovers
2013-09-30 15:46     ` "Paweł Hajdan, Jr."
2013-09-30 16:37     ` Markos Chandras
2013-10-01 13:45 ` 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=5248EA1F.3030202@gentoo.org \
    --to=phajdan.jr@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