You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lecharny <el...@iktek.com> on 2006/09/03 22:20:47 UTC

[ADS 2.0] discussions

Hi gang,

we have started some discussion relative to ADS 2.0 on the ML, and it 
could be good to be able to distinguish this thread from the other ones.

I suggest that we start all mails relative to ADS 2.0 by [ADS 2.0]

btw, this ADS-2.0 is not scheduled for a close future, let's say it's 
myuch more an experimental zone where we put some ideas we can't 
implement in 1.0 - but that we may put in 1.1 or 1.2 ...)

wdyt ?


Re: [ADS 2.0] discussions

Posted by Ersin Er <er...@gmail.com>.
Hi,

On 9/4/06, Trustin Lee <tr...@gmail.com> wrote:
> Hi Emmanuel,
>
>
> On 9/4/06, Emmanuel Lecharny <el...@iktek.com> wrote:
> > Hi gang,
> >
> > we have started some discussion relative to ADS 2.0 on the ML, and it
> > could be good to be able to distinguish this thread from the other ones.
> >
> > I suggest that we start all mails relative to ADS 2.0 by [ADS 2.0]
> >
> > btw, this ADS-2.0 is not scheduled for a close future, let's say it's
> > myuch more an experimental zone where we put some ideas we can't
> > implement in 1.0 - but that we may put in 1.1 or 1.2 ...)
>
>
> I don't think we can't experiment with 1.1 or any further releases.  I
> thought we are rewriting ApacheDS completely from the number 2.0.
>
> What we really need to do is to extract important design issues of ApacheDS
> from a various level (API, architecture, ...) and resolve them one by one in
> decending order of the impact.  I think this effort should make what 1.1 is.
>  Yep, as we discussed long before, 1.1 is a unstable branch.  So basically
> we shouldn't have any limitation on changing anything critical.  Resolving a
> big design issue which causes a lot of refactoring and rewriting should be
> done as earliest as possible in a unstable branch.

IMO, 1.1 branch still seems to be a "lesson" taking branch. It's main
purpose is testing very new features. And with all those lessons, 2.0
can be written from scratch.

> 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


-- 
Ersin

Re: [ADS 2.0] discussions

Posted by Alex Karasulu <ao...@bellsouth.net>.
Trustin Lee wrote:
> Hi Emmanuel,
> 
> On 9/4/06, *Emmanuel Lecharny* <elecharny@iktek.com 
> <ma...@iktek.com>> wrote:
> 
>     Hi gang,
> 
>     we have started some discussion relative to ADS 2.0 on the ML, and it
>     could be good to be able to distinguish this thread from the other ones.
> 
>     I suggest that we start all mails relative to ADS 2.0 by [ADS 2.0]
> 
>     btw, this ADS-2.0 is not scheduled for a close future, let's say it's
>     myuch more an experimental zone where we put some ideas we can't
>     implement in 1.0 - but that we may put in 1.1 or 1.2 ...)
> 
> 
> I don't think we can't experiment with 1.1 or any further releases.  I 
> thought we are rewriting ApacheDS completely from the number 2.0.

Right 2.0 is rewrite with 1.5 jdk while 1.1, 1.2 ... is not and still 
uses jdk 1.4.

> What we really need to do is to extract important design issues of 
> ApacheDS from a various level (API, architecture, ...) and resolve them 
> one by one in decending order of the impact.  

I agree with you 100%.

I think this effort should
> make what 1.1 is. 

+1 here too.

  Yep, as we discussed long before, 1.1 is a unstable
> branch.  So basically we shouldn't have any limitation on changing 
> anything critical.  

Exactly.

Resolving a big design issue which causes a lot of
> refactoring and rewriting should be done as earliest as possible in a 
> unstable branch.
> 

I cannot agree with you more.

Alex

Re: [ADS 2.0] discussions

Posted by Emmanuel Lecharny <el...@gmail.com>.
Trustin Lee a écrit :

> I don't think we can't experiment with 1.1 or any further releases.  I 
> thought we are rewriting ApacheDS completely from the number 2.0.

Yes, this is the case. May be my previous mail was not completly clear. 
What I meant is :
- 2.0 is a complete rewriting
- 1.1, 1.3, etc are experimental implementations of new features and 
improvment over previous features
- 1.2, 1.4, etc are stable versions

>
> What we really need to do is to extract important design issues of 
> ApacheDS from a various level (API, architecture, ...) and resolve 
> them one by one in decending order of the impact.  I think this effort 
> should make what 1.1 is.

I agree. But in the same time, while rewriting the whole server in 2.0, 
we may found new solution that could be included in 1.1. Remember that 
2.0 will be Java 5, so it will be different from 1.1, even if the code 
base could be very close. The idea is to let users get better versions 
really soon, not to let them wait for one year before they can 
experiment 2.0. So, yes, 1.1 and 2.0 will evolve in parallel.

> Yep, as we discussed long before, 1.1 is a unstable branch.  So 
> basically we shouldn't have any limitation on changing anything 
> critical.  Resolving a big design issue which causes a lot of 
> refactoring and rewriting should be done as earliest as possible in a 
> unstable branch.

Exactly.

Emmanuel

Re: [ADS 2.0] discussions

Posted by Trustin Lee <tr...@gmail.com>.
Hi Emmanuel,

On 9/4/06, Emmanuel Lecharny <el...@iktek.com> wrote:
>
> Hi gang,
>
> we have started some discussion relative to ADS 2.0 on the ML, and it
> could be good to be able to distinguish this thread from the other ones.
>
> I suggest that we start all mails relative to ADS 2.0 by [ADS 2.0]
>
> btw, this ADS-2.0 is not scheduled for a close future, let's say it's
> myuch more an experimental zone where we put some ideas we can't
> implement in 1.0 - but that we may put in 1.1 or 1.2 ...)


I don't think we can't experiment with 1.1 or any further releases.  I
thought we are rewriting ApacheDS completely from the number 2.0.

What we really need to do is to extract important design issues of ApacheDS
from a various level (API, architecture, ...) and resolve them one by one in
decending order of the impact.  I think this effort should make what
1.1is.  Yep, as we discussed long before,
1.1 is a unstable branch.  So basically we shouldn't have any limitation on
changing anything critical.  Resolving a big design issue which causes a lot
of refactoring and rewriting should be done as earliest as possible in a
unstable branch.

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