You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2004/06/08 03:15:19 UTC

[VOTE] Leo Sutix as committer Was: [Sandbox/Attributes] Promotion

I see no reason not to have Leo as a committer and have him guide
commons-attributes to a release. So:

[  ] +1 Yep
[  ] -1 Nope

Hen

---------- Forwarded message ----------
Date: Mon, 7 Jun 2004 22:58:14 +0200
From: Leo Sutic <le...@gmail.com>
Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
To: commons-dev@jakarta.apache.org
Subject: [Sandbox/Attributes] Promotion and Release (some help needed)

All,

I have received emails to the effect that releasing Attributes as-is
would be a good idea. People need an official release to distribute
and to use in their own releases.

The documentation isn't perfect - I'm lacking a Maven demo to
complement the Ant demo, but I don't think that the docs are bad
enough to warrant holding up the release.

Since Attributes is in the sandbox right now, it has to be promoted.
And this is a problem. See, I'm not a commons committer. So promoting
the project would mean that its chief developer (me) suddenly can't
commit code to it. This is not an acceptable state.

So, the way I see it - these are the ways forward:

 1. Attributes stay in sandbox, unreleased.
 2. Attributes stay in sandbox, but we release it.
 3. Attributes move to commons proper, we release it, and I get
committer status.

Of these, (3) is the most preferred one, followed by (2) and (1).

Commons Committers, what do you say?

/LS

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


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


Re: [VOTE] Leo Sutix as committer Was: [Sandbox/Attributes] Promotion

Posted by Dion Gillard <di...@gmail.com>.
+1 on Leo.

On Mon, 7 Jun 2004 21:15:19 -0400 (EDT), Henri Yandell
<ba...@generationjava.com> wrote:
> 
> 
> I see no reason not to have Leo as a committer and have him guide
> commons-attributes to a release. So:
> 
> [  ] +1 Yep
> [  ] -1 Nope
> 
> Hen
> 
> ---------- Forwarded message ----------
> Date: Mon, 7 Jun 2004 22:58:14 +0200
> From: Leo Sutic <le...@gmail.com>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: commons-dev@jakarta.apache.org
> Subject: [Sandbox/Attributes] Promotion and Release (some help needed)
> 
> All,
> 
> I have received emails to the effect that releasing Attributes as-is
> would be a good idea. People need an official release to distribute
> and to use in their own releases.
> 
> The documentation isn't perfect - I'm lacking a Maven demo to
> complement the Ant demo, but I don't think that the docs are bad
> enough to warrant holding up the release.
> 
> Since Attributes is in the sandbox right now, it has to be promoted.
> And this is a problem. See, I'm not a commons committer. So promoting
> the project would mean that its chief developer (me) suddenly can't
> commit code to it. This is not an acceptable state.
> 
> So, the way I see it - these are the ways forward:
> 
>  1. Attributes stay in sandbox, unreleased.
>  2. Attributes stay in sandbox, but we release it.
>  3. Attributes move to commons proper, we release it, and I get
> committer status.
> 
> Of these, (3) is the most preferred one, followed by (2) and (1).
> 
> Commons Committers, what do you say?
> 
> /LS
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

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


Re: [VOTE] Leo Sutix as committer Was: [Sandbox/Attributes] Promotion

Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
> I see no reason not to have Leo as a committer and have him guide
> commons-attributes to a release. So:
> 
> [ X ] +1 Yep
> [  ] -1 Nope

Also +1 for promoting attributes to commons proper.

Phil



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


Re: [VOTE] Leo Sutix as committer Was: [Sandbox/Attributes] Promotion

Posted by Alex Karasulu <ao...@bellsouth.net>.
+1 to Mr. Sutic

On Tue, 2004-06-08 at 01:52, Dirk Verbeeck wrote:
> +1
> 
> -- Dirk
> 
> Henri Yandell wrote:
> > I see no reason not to have Leo as a committer and have him guide
> > commons-attributes to a release. So:
> > 
> > [  ] +1 Yep
> > [  ] -1 Nope
> > 
> > Hen
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


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


Re: [VOTE] Leo Sutix as committer Was: [Sandbox/Attributes] Promotion

Posted by Dirk Verbeeck <di...@pandora.be>.
+1

-- Dirk

Henri Yandell wrote:
> I see no reason not to have Leo as a committer and have him guide
> commons-attributes to a release. So:
> 
> [  ] +1 Yep
> [  ] -1 Nope
> 
> Hen



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