Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates
 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=tFPnBlKEKlNuCLaUTEDDZMAz/mkGk/xuwq9vQPxWweuEYtoLhaDolJ9oUBiuupX/wU
         b9uFPGF1QnYjlZXIuP+GS9JH50i1LoUbqE0BXAvfaqD6jiNRH6wZmEQ4qWUgV6X0d8YI
         JvktbFCr8fGNFsf+R89cKzvdSqOUYd8b8dkuM=
Message-ID: <98d8c0860809170206m3a160c8dka7edcaa6391430d7@mail.gmail.com>
Date: Wed, 17 Sep 2008 11:06:44 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [vote] Release studio-plugin
In-Reply-To: <48D0C4F9.6080700@nextury.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_8487_25938231.1221642404072"
References: <48D09F11.50901@otego.com> <48D09F92.7010609@apache.org>
	 <98d8c0860809162342l698eeaddmc20c5b1815c50f4d@mail.gmail.com>
	 <48D0C282.6090408@nextury.com> <48D0C3BA.7020402@apache.org>
	 <48D0C4F9.6080700@nextury.com>

------=_Part_8487_25938231.1221642404072
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Emmanuel,

On Wed, Sep 17, 2008 at 10:51 AM, Emmanuel Lecharny <elecharny@gmail.com>wrote:

> It's much more a question of who is using the released part. Atm, it's just
> us, the Server. Even studio don't use it.


It's the opposite... ;)
Studio uses it, Server doesn't.


> We have had the very same discussion 2 months ago about shared : should we
> vote on it? Right now, I think we should vote on what is used by more than
> one project, as it gives a chance to avoid problems. So here is the project
> I think we need to vote for :
> - Studio
> - Server
> - Shared
>
> All the other projects (project, plugins, daemon, etc) are only used
> internally by a single project, and are part of a bigger vote. You won't
> release Studio if the studio-plugin is dorked ...
>
> Does it makes sense ?


I don't completely agree, I think we need a vote for any release we make to
the Maven repository.

Sometimes people have pending modifications on a project, and having a vote
before releasing is a great way to avoid releasing something that is not
complete.
With a vote, the developer will be able to indicate that he needs to apply a
few modifications before the release is OK.

Although, I agree on the fact that we can do grouped votes, like the one I
did some time ago, where I launched two releases votes (one for Studio and
one for Shared - as Studio depends on it) in a single thread

Regards,
Pierre-Arnaud

------=_Part_8487_25938231.1221642404072
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi Emmanuel,<br><br>On Wed, Sep 17, 2008 at 10:51 AM, Emmanuel Lecharny <span dir="ltr">&lt;<a href="mailto:elecharny@gmail.com">elecharny@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

It&#39;s much more a question of who is using the released part. Atm, it&#39;s just us, the Server. Even studio don&#39;t use it.</blockquote><div><br>It&#39;s the opposite... ;)<br>Studio uses it, Server doesn&#39;t.<br>
&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We have had the very same discussion 2 months ago about shared : should we vote on it? Right now, I think we should vote on what is used by more than one project, as it gives a chance to avoid problems. So here is the project I think we need to vote for :<br>

- Studio<br>
- Server<br>
- Shared<br>
<br>
All the other projects (project, plugins, daemon, etc) are only used internally by a single project, and are part of a bigger vote. You won&#39;t release Studio if the studio-plugin is dorked ...<br>
<br>
Does it makes sense ?</blockquote><div><br>I don&#39;t completely agree, I think we need a vote for any release we make to the Maven repository.<br><br>Sometimes people have pending modifications on a project, and having a vote before releasing is a great way to avoid releasing something that is not complete.<br>
With a vote, the developer will be able to indicate that he needs to apply a few modifications before the release is OK.<br><br>Although, I agree on the fact that we can do grouped votes, like the one I did some time ago, where I launched two releases votes (one for Studio and one for Shared - as Studio depends on it) in a single thread<br>
<br>Regards,<br>Pierre-Arnaud <br></div></div><br></div>

------=_Part_8487_25938231.1221642404072--