Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 4088 invoked from network); 1 Feb 2011 23:56:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 23:56:33 -0000 Received: (qmail 57266 invoked by uid 500); 1 Feb 2011 23:56:33 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 57165 invoked by uid 500); 1 Feb 2011 23:56:33 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 57158 invoked by uid 99); 1 Feb 2011 23:56:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 23:56:32 +0000 X-ASF-Spam-Status: No, hits=-1997.8 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 01 Feb 2011 23:56:30 +0000 Received: (qmail 4028 invoked by uid 99); 1 Feb 2011 23:56:08 -0000 Received: from localhost.apache.org (HELO mail-gx0-f178.google.com) (127.0.0.1) (smtp-auth username elecharny, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 23:56:08 +0000 Received: by gxk25 with SMTP id 25so3235700gxk.37 for ; Tue, 01 Feb 2011 15:56:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.65.12 with SMTP id n12mr11652138aga.62.1296604567389; Tue, 01 Feb 2011 15:56:07 -0800 (PST) Reply-To: elecharny@apache.org Received: by 10.91.109.20 with HTTP; Tue, 1 Feb 2011 15:56:07 -0800 (PST) In-Reply-To: References: Date: Wed, 2 Feb 2011 00:56:07 +0100 Message-ID: Subject: Re: [Shared] Milestone Roadmap From: Emmanuel Lecharny To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=00163646da78a7450b049b414664 X-Virus-Checked: Checked by ClamAV on apache.org --00163646da78a7450b049b414664 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Feb 1, 2011 at 7:13 PM, Alex Karasulu wrote: > PURPOSE > ---------------- > > This is a summary of a milestone release plan Emmanuel and I came up with > off list. > > We would like to: > > (1) request feedback > (2) integrate feedback > (3) break out action items into JIRA tasks > (4) drive forward and execute > > > PRELUDE > ---------------- > > Now that trunk has stabilized, we will branch. An m1 branch will be creat= ed > here: > > https://svn.apache.org/repos/asf/directory/branches/m1 > =3D> SVN folder with externals to m1 branches in shared, studio= , > and apacheds > > We will work in branch m1 for large deltas, while merging point alteratio= ns > from trunks into branch m1. Each milestone will have different stages. A= t > the end of each stage, we will perform a check pointed stable merge back > into trunks. > > > M1 MILESTONE > ------------------------ > > Goals: > > o General cleanup, documentation, formatting, and test coverage > o Hide implementation details > o Restructure build for shared-ldap breakup > o Consolidated LDAP API aggregation module > > > Stages: > > (1) General cleanup of low hanging fruit: > - move tests to appropriate area > - adhere to package and class naming conventions > - correct obvious small coding errors > - add critical documentation > - add critical test coverage where missing > > > (2) Refactoring to hide implementation details > - decouple DSML parser from CODEC implementation classes > - decouple ADS and Studio from CODEC implementation classes > - clearly define CODEC API allowed for use in ADS, Studio, and > DSML > - separate out CODEC API from CODEC > > (3) Creation of modules in new build structure: > - create ldap-model > - create ldap-codec > - create ldap-codec-api > - create ldap-extensions > - delete ldap > - ldap-api =3D> aggregation only module for ldap-[client-api, > model, codec, codec-api] > There is one more important thing : currently, we are using the decorators we defined in shared-ldap into the dsml decoder. the '(2) decouple DSML parser from CODEC' point cover part of this thing, but the existing decorators should also be extracted from the CODEC, and probably renamed Asn1Decorator (as we should rename the DSML decorators DsmlDecorator) > > > M2 MILESTONE > ------------------------ > > Goals: > > o Apply extension patterns to extended requests and responses (like > controls) > o General cleanup, documentation, formatting, and test coverage > o Leverage embedded OSGi container (Felix) to enable extensions > o Setup in-situ testing of OSGi components in build > > ... > > At this point it makes little sense to us to continue further since thing= s > might change. Some of the M2 goals are there for food for thought. Perhap= s > we might break these up into 2 separate milestones, maybe not. > > Right now the focus is on M1, gaining consensus, applying feedback, and > then creating top level tasks in JIRA. Then we might want to add subtasks= in > JIRA to these mail goal based tasks. > > Thoughts? > perfect ! --=20 Regards, Cordialement, Emmanuel L=E9charny www.iktek.com --00163646da78a7450b049b414664 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Feb 1, 2011 at 7:13 PM, Alex Kar= asulu <akarasu= lu@apache.org> wrote:
PURPOSE
----------------

This is a summa= ry of a milestone release plan Emmanuel and I came up with off list. =A0
We would like to:

=A0=A0(1) request fee= dback
=A0=A0(2) integrate feedback
=A0=A0(3) break out action item= s into JIRA tasks
=A0=A0(4) drive forward and execute

PRELUDE
----------------

Now that trunk has stabilized, we will branch. An m1 branch = will be created here:

=A0=A0 =A0 =A0 =A0 =A0=3D> SVN folder with externals to m1 branches= in shared, studio, and apacheds

We will work in b= ranch m1 for large deltas, while merging point alterations from trunks into= branch m1. =A0Each milestone will have different stages. At the end of eac= h stage, we will perform a check pointed stable merge back into trunks.


M1 MILESTONE
-----------------= -------

Goals:

=A0=A0 o G= eneral cleanup, documentation, formatting, and test coverage
=A0= =A0 o Hide implementation details
=A0=A0 o Restructure build for shared-ldap breakup
=A0=A0 o = Consolidated LDAP API aggregation module


Stages:

=A0=A0 (1) General cleanup of low ha= nging fruit:
=A0=A0 =A0 =A0 =A0 =A0 - move tests to appropriate area
=A0= =A0 =A0 =A0 =A0 =A0 - adhere to package and class naming conventions
<= div>=A0=A0 =A0 =A0 =A0 =A0 - correct obvious small coding errors
= =A0=A0 =A0 =A0 =A0 =A0 - add critical documentation
=A0=A0 =A0 =A0 =A0 =A0 - add critical test coverage where missing


=A0=A0 (2) Refactoring to hide implemen= tation details
=A0=A0 =A0 =A0 =A0 =A0 - decouple DSML parser from= CODEC implementation classes
=A0=A0 =A0 =A0 =A0 =A0 - decouple ADS and Studio from CODEC implementa= tion classes
=A0=A0 =A0 =A0 =A0 =A0 - clearly define CODEC API al= lowed for use in ADS, Studio, and DSML
=A0=A0 =A0 =A0 =A0 =A0 - s= eparate out CODEC API from CODEC

=A0=A0(3) = Creation of modules in new build structure:
=A0=A0 =A0 =A0 =A0 = =A0 - create ldap-model
=A0=A0 =A0 =A0 =A0 =A0 - create ldap-codec
=A0=A0 =A0 =A0 = =A0 =A0 - create ldap-codec-api
=A0=A0 =A0 =A0 =A0 =A0 - create ldap-extensions
=A0=A0 =A0 = =A0 =A0 =A0 - delete ldap
=A0=A0 =A0 =A0 =A0 =A0 - ldap-api =3D&g= t; aggregation only module for ldap-[client-api, model, codec, codec-api]= =A0

There is one more important thing : currently, we are using the decorators = we defined in shared-ldap into the dsml decoder. the '(2) decouple DSML= parser from CODEC' point cover part of this thing, but the existing de= corators should also be extracted from the CODEC, and probably renamed Asn1= Decorator (as we should rename the DSML decorators DsmlDecorator)


M2 MILESTONE
------------------------

Goals:

=A0=A0 o Apply extension patterns to ext= ended requests and responses (like controls)
=A0=A0 o General cle= anup, documentation, formatting, and test coverage
=A0=A0 o Leverage embedded OSGi container (Felix) to enable extensions=
=A0=A0 o Setup in-situ testing of OSGi components in build
=

...

At this point it makes lit= tle sense to us to continue further since things might change. Some of the = M2 goals are there for food for thought. Perhaps we might break these up in= to 2 separate milestones, maybe not.

Right now the focus is on M1, gaining consensus, applyi= ng feedback, and then creating top level tasks in JIRA. Then we might want = to add subtasks in JIRA to these mail goal based tasks.

Thoughts?

perfect !
--
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com
--00163646da78a7450b049b414664--