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
 72.14.204.230 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=qGxzHxnrKbOHFUzkGVa34jansrru8d857wcBcVlyckuRZz6RH8wGLzRI1rIdtwTjYXPl8Y5NRxdlNYLtmgzT6nyylYcH0ITg+x+ssT//8nU12A40wPFKQ4fIVCO/iWdTvEO50aPeCB+CamxXs4moyFLiaXq7tgO8GHgopYDG4rg=
Message-ID: <98d8c0860803140701r7d3fcbbfq5c508369df337fc5@mail.gmail.com>
Date: Fri, 14 Mar 2008 15:01:28 +0100
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Studio unscheduled issues
In-Reply-To: <47DA56D5.9010003@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1571_20241711.1205503288394"
References: <47DA56D5.9010003@gmail.com>

------=_Part_1571_20241711.1205503288394
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

+1

Like you, I think we should not schedule for the 1.1.0 version issues that
can have a large impact (and bring regressions) to the 1.1.0 code base.

I'm going to create a 1.1.1 version in JIRA and have a look at the
unscheduled issues.

Thanks for the heads up.

Pierre-Arnaud


On Fri, Mar 14, 2008 at 11:43 AM, Emmanuel Lecharny <elecharny@gmail.com>
wrote:

> Hi guys,
>
> I just looked at the Studio issues ( I have 4 new issues to add). There
> are currently 3 issues affected to 1.1.0, 10 affected to 1.2.0 and 65
> unscheduled issues.
>
> It would be great, before releasing 1.1.0, to schedule the list of
> unscheduled issues. As 1.1.0 is now pretty stable, I'm not sure we
> should fix as much issues as possible in the 1.1.0 code base (because it
> may have impact on the 1.1.0), but at least, it may be a good thing to
> create a 1.1.1 release, and affect the issues to this release.
>
> wdyt ?
>
> --
> --
> cordialement, regards,
> Emmanuel L=E9charny
> www.iktek.com
> directory.apache.org
>
>
>

------=_Part_1571_20241711.1205503288394
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

+1<br><br>Like you, I think we should not schedule for the 1.1.0 version is=
sues that can have a large impact (and bring regressions) to the 1.1.0 code=
 base.<br><br>I&#39;m going to create a 1.1.1 version in JIRA and have a lo=
ok at the unscheduled issues.<br>
<br>Thanks for the heads up.<br><br>Pierre-Arnaud<br><br><br><div class=3D"=
gmail_quote">On Fri, Mar 14, 2008 at 11:43 AM, Emmanuel Lecharny &lt;<a hre=
f=3D"mailto:elecharny@gmail.com">elecharny@gmail.com</a>&gt; wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204,=
 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys,<br>
<br>
I just looked at the Studio issues ( I have 4 new issues to add). There<br>
are currently 3 issues affected to 1.1.0, 10 affected to 1.2.0 and 65<br>
unscheduled issues.<br>
<br>
It would be great, before releasing 1.1.0, to schedule the list of<br>
unscheduled issues. As 1.1.0 is now pretty stable, I&#39;m not sure we<br>
should fix as much issues as possible in the 1.1.0 code base (because it<br=
>
may have impact on the 1.1.0), but at least, it may be a good thing to<br>
create a 1.1.1 release, and affect the issues to this release.<br>
<br>
wdyt ?<br>
<br>
--<br>
<font color=3D"#888888">--<br>
cordialement, regards,<br>
Emmanuel L=E9charny<br>
<a href=3D"http://www.iktek.com" target=3D"_blank">www.iktek.com</a><br>
<a href=3D"http://directory.apache.org" target=3D"_blank">directory.apache.=
org</a><br>
<br>
<br>
</font></blockquote></div><br>

------=_Part_1571_20241711.1205503288394--