From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Java 1.5 migration plans
Date: Mon, 09 Jan 2006 22:54:13 -0500 [thread overview]
Message-ID: <43C32FE5.2010901@gentoo.org> (raw)
In-Reply-To: <43C2E6DF.7000702@gmx.net>
Martin von Gagern wrote:
> I added a list of little steps at the end of the guide. I don't know how
> the assignment of devs to tasks usually works, but it would be great if
> we could fill the list with assigned persons and estimated times.
>
> Greetings,
> Martin von Gagern
>
The list of steps definitely looks good, and gives us a good plan of
attack. Overall, the migration plan looks really good, although I'm
still trying to get a few for a few bits of it, particularly when/how
we'd migrate to the 'next gen' style of ebuilds.
Before going forward with the plan, though, it would probably be a good
idea for all the java devs to, you know, agree to go through with this
plan :) This is particularly important because we would be the ones
actually committing these to portage. I'd say we're at the point where
we could/should have a meeting in #gentoo-java to go over this.
As far as taking up particular tasks and whatnot, I'm not particular
sure myself, being the new guy and all. But given that all work is
voluntary anyways, I'd imagine people would volunteer for taking care of
this or that task.
- Josh (nichoj)
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2006-01-10 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 6:58 [gentoo-java] Java 1.5 migration plans Joshua Nichols
2005-12-30 19:40 ` Thomas Matthijs
2005-12-30 20:14 ` Petteri Räty
2005-12-31 1:55 ` Martin von Gagern
2006-01-06 22:53 ` Thomas Matthijs
2006-01-07 1:07 ` Martin von Gagern
2006-01-09 22:42 ` Martin von Gagern
2006-01-10 3:54 ` Joshua Nichols [this message]
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=43C32FE5.2010901@gentoo.org \
--to=nichoj@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