From: "William L. Thomson Jr." <wltjr@gentoo.org>
To: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Weka package cleanup
Date: Tue, 16 Jan 2007 19:22:46 -0500 [thread overview]
Message-ID: <1168993366.13072.23.camel@wlt.obsidian-studios.com> (raw)
In-Reply-To: <93e475bc0701161607s5ca219fcx1a03cca7f6acbfc3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Wed, 2007-01-17 at 13:07 +1300, Alistair Bush wrote:
>
> Basically the aim I have for this is too draw the attention of you
> dev's to bugs that are a 'quick' fix.
>
> Therefore meeting the aim of closing bugs without you guys having to
> do most of the investigation...
Sounds good to me :)
> I have also though of going thru bugs.gentoo.org and reassigning the
> priority of bugs into categories
I don't think anyone would really object to that, other than maybe some
bug spam.
> I also believe that there should be some bugs marked as WONTFIX,
> CANTFIX.
Yes, those are great. Would be nice if there was a YOUFIX :)
> For example jboss https://bugs.gentoo.org/show_bug.cgi?id=148383 and
> https://bugs.gentoo.org/show_bug.cgi?id=66965
>
> I believe, and it will be interesting in hereing your views on this,
> that bugs should only be open if they are actually going to be worked
> on.
Well since they are stuff that's in tree, in theory they should remain
open. Till there is an alternative in tree, or fix. Otherwise closing
might just cause someone else to file a new bug instead of finding the
pre-existing closed one.
> With jboss we now have a binary ebuild in the overlay that could
> replace the existing versions and these jboss bugs could be closed.
Adding binary to tree, ew. Bugs closed, good.
--
William L. Thomson Jr.
Gentoo/Java
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-17 0:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 19:32 [gentoo-java] Weka package cleanup Alistair Bush
2007-01-16 20:04 ` Petteri Räty
2007-01-16 20:34 ` Alon Bar-Lev
2007-01-16 20:51 ` Vlastimil Babka
2007-01-16 20:55 ` Alon Bar-Lev
2007-01-16 22:53 ` Alistair Bush
2007-01-16 23:23 ` Alistair Bush
2007-01-16 23:37 ` William L. Thomson Jr.
2007-01-17 0:07 ` Alistair Bush
2007-01-17 0:22 ` William L. Thomson Jr. [this message]
2007-01-17 0:59 ` Vlastimil Babka
2007-01-17 1:08 ` Alistair Bush
2007-01-17 1:54 ` Alistair Bush
2007-01-17 6:39 ` Joshua Nichols
2007-01-17 7:02 ` William L. Thomson Jr.
2007-01-17 0:09 ` William L. Thomson Jr.
2007-01-16 23:35 ` William L. Thomson Jr.
2007-01-19 12:48 ` Petteri Räty
2007-01-19 19:12 ` [gentoo-java] dev-java/aspectwerkz Alistair Bush
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=1168993366.13072.23.camel@wlt.obsidian-studios.com \
--to=wltjr@gentoo.org \
--cc=gentoo-java@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