public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Krzysztof Pawlik <nelchael@gentoo.org>
To: Gentoo Java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] QA: java-experimental
Date: Sun, 01 Feb 2009 11:31:40 +0000	[thread overview]
Message-ID: <4985881C.2010907@gentoo.org> (raw)
In-Reply-To: <49858190.10505@gentoo.org>

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

Alistair Bush wrote:
> I will look into this at some point.  I suppose there are many things we
> could do to help maintain qa.  I suppose we also need more overview of
> our contributors.  So I might attempt to generate reports, etc of
> commits by those users.

So.. maybe it's time to re-think the way java-* overlays are used? I'd opt for
"staging" approach: let java-experimental be well, experimental - you don't know
whenever something will work, is a good idea, you're still working on it, etc.
java-overlay would become a staging ground: after some time (to be defined)
ebuilds would end in main tree.

So the ebuild migration would look like:
 * experimental: fresh stuff
 * overlay: checked by somebody else (peer reviewed)
 * main tree: after some time in overlay (like a month)

That would enforce from where one can have dependencies in particular overlay,
would (hopefully) reduce the size of overlays.

Something similar was done:
http://overlays.gentoo.org/proj/java/wiki/March_2007_Summary#Changesinoverlays

-- 
Krzysztof Pawlik   <nelchael at gentoo.org>   key id: 0xBC555551
desktop-misc, java, apache, ppc, vim, kernel, python...


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

  reply	other threads:[~2009-02-01 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01  2:11 [gentoo-java] QA: java-experimental Alistair Bush
2009-02-01 10:32 ` Krzysztof Pawlik
2009-02-01 11:03   ` Alistair Bush
2009-02-01 11:31     ` Krzysztof Pawlik [this message]
2009-02-01 18:33       ` 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=4985881C.2010907@gentoo.org \
    --to=nelchael@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