public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tobias Klausmann <klausman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] Improve policy of stabilizations
Date: Sat, 7 Nov 2009 15:14:44 +0100	[thread overview]
Message-ID: <20091107141444.GA28658@eric.schwarzvogel.de> (raw)
In-Reply-To: <4AF331B0.4020108@gentoo.org>

Hi! 

On Thu, 05 Nov 2009, Petteri Räty wrote:
> In the past when smaller arches were not that active we used to
> mark Java packages stable after testing by at least one arch
> team. The probability to find arch specific issues in something
> like Java is not so high so I think arrangements like this are
> acceptable when the arch teams have problems keeping up.

For alpha, the java keywording policy is easy: don't.

We currently don't have any working JVM/JRE/JDK, so there's no
point in adding Java packages.

We *do* have dev-java/java-config keyworded, though the reason
escapes me at the moment :)

Regards,
Tobias

-- 
printk("NONONONOO!!!!\n");
        linux-2.6.6/drivers/atm/zatm.c



  parent reply	other threads:[~2009-11-07 14:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 16:36 [gentoo-dev] [RFC] Improve policy of stabilizations Arfrever Frehtes Taifersar Arahesis
2009-11-01 16:55 ` Mart Raudsepp
2009-11-01 18:19   ` Richard Freeman
2009-11-01 20:21     ` Petteri Räty
2009-11-01 21:16 ` [gentoo-dev] " Ryan Hill
2009-11-02 14:17 ` Christian Faulhammer
2009-11-02 15:23   ` Markos Chandras
2009-11-03 18:10     ` Christian Faulhammer
2009-11-04 12:36       ` Ben de Groot
2009-11-04 12:50         ` Christian Faulhammer
2009-11-04 18:01           ` Tobias Klausmann
2009-11-04 20:49             ` Nirbheek Chauhan
2009-11-04 21:02         ` Joseph Jezak
2009-11-05  3:48           ` Ryan Hill
2009-11-05  9:17             ` Tobias Klausmann
2009-11-05 20:12               ` Petteri Räty
2009-11-06  3:06                 ` Joseph Jezak
2009-11-06 14:18                 ` Nirbheek Chauhan
2009-11-06 14:45                   ` Fabian Groffen
2009-11-06 17:06                     ` Nirbheek Chauhan
2009-11-06 17:08                       ` Nirbheek Chauhan
2009-11-07  5:13                       ` Ryan Hill
2009-11-06 22:07                     ` Zac Medico
2009-11-07  3:36                       ` Arfrever Frehtes Taifersar Arahesis
2009-11-07 14:54                       ` Peter Volkov
2009-11-07 20:49                         ` Zac Medico
2009-11-08  0:12                           ` Nirbheek Chauhan
2009-11-08  9:31                             ` Petteri Räty
2009-11-08 12:55                           ` Peter Volkov
2009-11-09  2:34                             ` Zac Medico
2009-11-08  9:05                         ` Fabian Groffen
2009-11-08 12:53                           ` Peter Volkov
2009-11-06 22:52                     ` Rémi Cardona
2009-11-07  7:22                       ` Hans de Graaff
2009-11-06 16:00                   ` Kent Fredric
2009-11-06 17:00                     ` Nirbheek Chauhan
2009-11-07 14:14                 ` Tobias Klausmann [this message]
2009-11-05 10:52             ` Duncan
2009-11-06 17:18             ` Christian Faulhammer
2009-11-06 17:15           ` Christian Faulhammer

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=20091107141444.GA28658@eric.schwarzvogel.de \
    --to=klausman@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