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 (asf.osuosl.org: domain of trustin@gmail.com designates
 64.233.182.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=lciab/RYjGXatoEm1RspATPkcq/Svz2/qLxg9m1n0dtQ/0iAjdklsl5vKO6m/sJNH6my6UrXvGHxgCPzEqCMKarmJaNDJIl5bqbsOGfx127vLf+CG5RVbTa950MNR1dmdzZiam7EVUN6cc3ZNHwm8gEDGJqpy66UkiaMqfT0meQ=
Message-ID: <768dcb2e0602241803r7355b6f6v28979137b3b1df3d@mail.gmail.com>
Date: Sat, 25 Feb 2006 11:03:41 +0900
From: "Trustin Lee" <trustin@gmail.com>
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Convo summary: Procedures for Directory committers working on
 trunks
In-Reply-To: <a1b4a6610602241401x48ae7d21ibd47500346f4a652@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_23684_17136397.1140833021071"
References: <a1b4a6610602241338j2fb84709m767fab4ba555e87@mail.gmail.com>
	 <43FF7FB1.2030701@gmail.com>
	 <a1b4a6610602241401x48ae7d21ibd47500346f4a652@mail.gmail.com>

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

Everything sounds reasonable.

On 2/25/06, Ersin Er <ersin.er@gmail.com> wrote:
>
> > >*** And an offer from Alex: Breakage in trunks is not acceptable, so a
> > >committer who causes breakage in main branches or trunks will be
> > >responsible for making documentation for one week. A punishment ;-)
> > >(And yes, we need doco!)
> > >
> > >
> > What about writing new unit-tests? Or checking the code for style
> > violation? Ah, sorry, we don't have any style, isn't it? ;-)
>
> I agree for writing unit tests. And for style, Alex has added his
> eclipse formatter's xml to trunks. It may be a starting point. And yes
> we need a style doco ;-)


I agree for writing unit tests, too. :)

Cheers,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

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

Everything sounds reasonable.<br><br>On 2/25/06, <b class=3D"gmail_senderna=
me">Ersin Er</b> &lt;<a href=3D"mailto:ersin.er@gmail.com">ersin.er@gmail.c=
om</a>&gt; wrote:<div><span class=3D"gmail_quote"></span><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&gt; &gt;*** And an offer from Alex: Breakage in trunks is not acceptable, =
so a<br>&gt; &gt;committer who causes breakage in main branches or trunks w=
ill be<br>&gt; &gt;responsible for making documentation for one week. A pun=
ishment ;-)
<br>&gt; &gt;(And yes, we need doco!)<br>&gt; &gt;<br>&gt; &gt;<br>&gt; Wha=
t about writing new unit-tests? Or checking the code for style<br>&gt; viol=
ation? Ah, sorry, we don't have any style, isn't it? ;-)<br><br>I agree for=
 writing unit tests. And for style, Alex has added his
<br>eclipse formatter's xml to trunks. It may be a starting point. And yes<=
br>we need a style doco ;-)</blockquote><div><br>I agree for writing unit t=
ests, too. :)<br><br>Cheers,<br>Trustin<br></div></div>-- <br>what we call =
human nature is actually human habit
<br>--<br><a href=3D"http://gleamynode.net/">http://gleamynode.net/</a><br>=
--<br>PGP key fingerprints:<br>* E167 E6AF E73A CBCE EE41&nbsp;&nbsp;4A29 5=
44D DE48 FE95 4E7E<br>* B693 628E 6047 4F8F CFA4&nbsp;&nbsp;455E 1C62 A7DC =
0255 ECA6

------=_Part_23684_17136397.1140833021071--