Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <477BDEAF.5040100@it20one.at>
Date: Wed, 02 Jan 2008 19:57:51 +0100
From: Siegfried Goeschl <siegfried.goeschl@it20one.at>
Reply-To: siegfried.goeschl@it20one.at
Organization: IT20one GmbH
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Jakarta Commons Developers List <dev@commons.apache.org>
Subject: [exec] how to proceed for a nearly dormant project
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi folks,

I fixed a few things on commons-exec but I'm not sure how to proceed
from here since I'm the last/only man standing.

1) I nearly finished the open issue and need to do some field testing -
and I would need some help on more exotic platforms ... :-)

2) if everything is okay I would like to release commons-exec-1.0.0

3) not sure if I'm  proper commons committer but somehow SVN access
works for the sandbox SVN

4) I assume that I need a PMC to cut a RC and the release later on - is
this correct?

5) recently there was a lot of discussion regarding release and parent
poms - I'm currently using commons-sandbox-parent-3-SNAPSHOT which might
not be good enough for a release considering the maven-release-plugin.
Is there a non-SNAPSHOT parent pom or can a release be only done from a
commons-proper project

Thanks in advance

Siegfried Goeschl


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org