From: Caster <cast3r@seznam.cz>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Gentoo/Java staffing needs
Date: Sat, 29 Jul 2006 00:31:40 +0200 [thread overview]
Message-ID: <44CA904C.6030307@seznam.cz> (raw)
In-Reply-To: <44CA2E9A.9070802@gentoo.org>
Joshua Nichols wrote:
> Miroslav Šulc wrote:
>> I thought that you are busy but I'm not sure whether I should submit
>> bugs on experimental java to bugzilla. Maybe I do not understand the
>> "experimental" word correctly. Does it mean a "lab" or "just before
>> moving to sync"?
>>
> Both really. Although, maybe it would make sense to have separate
> overlays for things that really are 'experimental' versus things that
> are ready to go into the tree.
I agree. And people willing to help but not having the time/etc to
become full gentoo devs could have commit access to the "more
experimental" overlay and from there devs could review the ebuilds and
if they are fine, move to the "ready/reviewed" overlay (or even main
tree) - I think it's how the infamous Sunrise overlay works :) I think
svn is nicer to work with than sending stuff to maillist or uploading to
bugzilla, then dev needs to put it to his overlay himself for review,
seems like unnecessary waste of time to me.
>> I can place those ebuilds I sent you to bugzilla if you want me to,
>> that's not a problem. Anyway I would appreciate feedback on the ebuilds
>> because these are my first java ebuilds and I sure missed something.
>>
> That certainly wouldn't hurt, putting them up on bugzilla.
>
Well, if they could be assigned to directly. Now it goes to bug
wranglers, and sometimes the reactions on java bugs aren't very warm, as
I can see on #gentoo-bugs :( Also, we often need to reassure Jakub that
the our bug report isn't invalid because of not following migration
guide etc... Maybe trac tickets could be better for making todo notes of
stuff so it's somehow organized and not forgotten. There was tickets
module in gentooexperimental.org Trac, but I can't see it on
overlays.g.o though...
Just my 2c
Caster
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-28 22:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 20:46 [gentoo-java] Gentoo/Java staffing needs Joshua Nichols
2006-07-28 8:13 ` [gentoo-java] " Ted Kosan
2006-07-28 9:06 ` Caster
2006-07-29 4:08 ` Joshua Nichols
2006-07-28 9:02 ` [gentoo-java] " Miroslav Šulc
2006-07-29 4:13 ` Joshua Nichols
2006-07-29 10:59 ` Miroslav Šulc
2006-07-29 14:54 ` Joshua Nichols
2006-07-29 15:12 ` Ernst de Haan
2006-07-29 17:38 ` Miroslav Šulc
2006-07-28 14:17 ` Wiktor Wandachowicz
2006-07-28 14:44 ` Miroslav Šulc
2006-07-28 14:57 ` William L. Thomson Jr.
[not found] ` <15435f760607280751j66736f3epce2736804af29328@mail.gmail.com>
2006-07-28 15:01 ` Miroslav Šulc
2006-07-28 15:13 ` Joshua Nichols
2006-07-28 15:23 ` Miroslav Šulc
2006-07-28 15:34 ` Joshua Nichols
2006-07-28 22:31 ` Caster [this message]
2006-07-28 22:55 ` Miroslav Šulc
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=44CA904C.6030307@seznam.cz \
--to=cast3r@seznam.cz \
--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