From dev-return-24606-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Mar 31 20:39:16 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 15428 invoked from network); 31 Mar 2008 20:39:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Mar 2008 20:39:16 -0000 Received: (qmail 24003 invoked by uid 500); 31 Mar 2008 20:39:15 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 23959 invoked by uid 500); 31 Mar 2008 20:39:15 -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 23948 invoked by uid 99); 31 Mar 2008 20:39:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 13:39:15 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.162.183 as permitted sender) Received: from [209.85.162.183] (HELO el-out-1112.google.com) (209.85.162.183) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 20:38:35 +0000 Received: by el-out-1112.google.com with SMTP id o28so596581ele.3 for ; Mon, 31 Mar 2008 13:38:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=cDNcZZzR4IdWHRehkmUiXPnuN+q0TG21qAoa1Xyrsv8=; b=ByCH0Aw9ji0dTNfvz/RonN1Hku7lBRAnjSv5+dm6HOsfgCBcVNWHevwEz+U/ATZrDaznmr5HYKipBjDC+68MdktIJymkuAcGjhofvPHZj074qmehe6n507qAhyaSVS4jxT8iQuZ+n5LY9tCypw3JVL+fM7uFwNWIiMAQPQud/lo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=Vh+kZQmTiso2kNy94Q1hi/JivHG5WLfFweXXgIpRF5JwtarCCMsHJmny7ULjM0yqhNWaHpPQCRE6p7lurq6ES8LDu5QWtG2RXA38zbUS2w8SloL98xcjyrtnnvzgcIeGyZlcpT0vTfp98B3r/kW2Kbnes2b0ILt0/wsiGfk6XMw= Received: by 10.141.193.1 with SMTP id v1mr2624991rvp.73.1206995919757; Mon, 31 Mar 2008 13:38:39 -0700 (PDT) Received: by 10.141.113.13 with HTTP; Mon, 31 Mar 2008 13:38:39 -0700 (PDT) Message-ID: Date: Mon, 31 Mar 2008 16:38:39 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Preparing to release In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10037_20645429.1206995919709" References: X-Google-Sender-Auth: c6d6d62a8eafa90c X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_10037_20645429.1206995919709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline What's remaining ... DIRSERVER-832 Added Attributes are all case sensitive DIRSERVER-956 Aborting a client search does not stop the search DIRSERVER-957 OOM when adding a lot of entries DIRSERVER-955 FilterMatch permissions are not being handled in Access Control decisions On Mon, Mar 31, 2008 at 7:06 AM, Alex Karasulu wrote: > In preparation for a pre ApacheCon release (1.5.2), I will start fixing > issues today and probably tomorrow. > > Alex > > > On Thu, Mar 27, 2008 at 12:33 PM, Alex Karasulu > wrote: > > > Hi all, > > > > We have not had a release in over 9 months. We've fixed many issues, > > introduced features (i.e. StartTLS, revamped installers etc) and > > improved the server quite a bit. Also with ApacheCon on the horizon I think > > it makes sense to get a release out the door. > > > > Since 1.5 is a feature introduction branch there's no need to close all > > issues open. I do recommend we do solve the blocking issues and perhaps > > consider other critical issues. Right now we only have the following > > blockers: > > > > DIRSERVER-1149 Removing a non existing value of an attribute removes one > > of this attribute's values > > DIRSERVER-957 OOM when adding a lot of entries > > DIRSERVER-832 Added Attributes are all case sensitive > > > > DIRSERVER-832 is not a blocker but could result in other bugs we have > > yet to discover. It's going to go away when the Entry API is completely put > > in position and the Cursor code is merged to use the Entry API. So it can > > wait. > > > > These are the remaining critical issues: > > > > DIRSERVER-1155 Use the rollback mechanism to restore the base when > > schema is modified > > - this is not critical IMO > > DIRSERVER-731 Streaming big objects > > - this is critical but not a must have for this release > > DIRSERVER-833 Attribute(s)Impl usage and API > > - again not critical and will be complete when bigbang is complete > > DIRSERVER-882 Adding a tool to convert Schema files to Ldif Files > > - not a critical feature (nice to have though) users can leverage > > studio for the time being > > DIRSERVER-956 Aborting a client search does not stop the search > > - CRITICAL > > DIRSERVER-959 We nedd a global cache > > - not critical - this is just a feature to do away with per partition > > entry cache (we can live with it) > > DIRSERVER-990 2 objects of the Apache DS Schema share the same OID > > - CRITICAL > > DIRSERVER-997 Block search ability for userPassword attribute > > - can wait until another release before going GA > > DIRSERVER-1083 Search on an custom attribute added to the dynamic schema > > fails when no result is found > > - CRITICAL > > DIRSERVER-465 Make partitions nestable: remove the nexus singleton! > > - can wait > > DIRSERVER-646 Replacing an unknown attribute with no values (deletion) > > causes an error > > - CRITICAL > > DIRSERVER-1056 Cleaning the warnings > > - can wait > > DIRSERVER-1064 Admin password cannot be hashed > > - this has been fixed > > DIRSERVER-798 Configurable ApacheDS OSGi bundles require schema oid > > assignments > > - can wait > > DIRSERVER-955 FilterMatch permissions are not being handled in Access > > Control decisions > > - need more investigation > > > > So personally I would consider the following issues on our plate for > > this release: > > > > DIRSERVER-1149 Removing a non existing value of an attribute removes one > > of this attribute's values > > DIRSERVER-957 OOM when adding a lot of entries > > DIRSERVER-832 Added Attributes are all case sensitive > > DIRSERVER-956 Aborting a client search does not stop the search > > DIRSERVER-990 2 objects of the Apache DS Schema share the same OID > > DIRSERVER-1083 Search on an custom attribute added to the dynamic schema > > fails when no result is found > > DIRSERVER-646 Replacing an unknown attribute with no values (deletion) > > causes an error > > > > This needs more investigation: > > > > DIRSERVER-955 FilterMatch permissions are not being handled in Access > > Control decisions > > > > I think we can knock these out pretty rapidly. If we cannot do so by > > Wednesday of next week I recommend we release anyway. There's no reason why > > we should not. 1.5.2 is a feature introduction release that does not > > guarantee a bug free server. Users would probably prefer to have a > > trackable release with these new features as a line in the sand to test > > against. > > > > Also I want to fix the present installer situation so we have installers > > once again for our latest release. > > > > Thoughts? > > > > Alex > > > > > ------=_Part_10037_20645429.1206995919709 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline What's remaining ...

DIRSERVER-832 Added Attributes are all case sensitive
DIRSERVER-956 Aborting a client search does not stop the search
DIRSERVER-957 OOM when adding a lot of entries
DIRSERVER-955 FilterMatch permissions are not being handled in Access Control decisions


On Mon, Mar 31, 2008 at 7:06 AM, Alex Karasulu <akarasulu@apache.org> wrote:
In preparation for a pre ApacheCon release (1.5.2), I will start fixing issues today and probably tomorrow. 

Alex


On Thu, Mar 27, 2008 at 12:33 PM, Alex Karasulu <akarasulu@apache.org> wrote:
Hi all,

We have not had a release in over 9 months.  We've fixed many issues, introduced features (i.e. StartTLS, revamped installers etc) and improved the server quite a bit.  Also with ApacheCon on the horizon I think it makes sense to get a release out the door. 

Since 1.5 is a feature introduction branch there's no need to close all issues open.  I do recommend we do solve the blocking issues and perhaps consider other critical issues.  Right now we only have the following blockers:

DIRSERVER-1149 Removing a non existing value of an attribute removes one of this attribute's values
DIRSERVER-957 OOM when adding a lot of entries
DIRSERVER-832 Added Attributes are all case sensitive

DIRSERVER-832 is not a blocker but could result in other bugs we have yet to discover.  It's going to go away when the Entry API is completely put in position and the Cursor code is merged to use the Entry API.  So it can wait.

These are the remaining critical issues:

DIRSERVER-1155 Use the rollback mechanism to restore the base when schema is modified
  - this is not critical IMO
DIRSERVER-731 Streaming big objects
  - this is critical but not a must have for this release
DIRSERVER-833 Attribute(s)Impl usage and API
  - again not critical and will be complete when bigbang is complete
DIRSERVER-882 Adding a tool to convert Schema files to Ldif Files
  - not a critical feature (nice to have though) users can leverage studio for the time being
DIRSERVER-956 Aborting a client search does not stop the search
  - CRITICAL
DIRSERVER-959 We nedd a global cache
  - not critical - this is just a feature to do away with per partition entry cache (we can live with it)
DIRSERVER-990 2 objects of the Apache DS Schema share the same OID
  - CRITICAL
DIRSERVER-997 Block search ability for userPassword attribute
  - can wait until another release before going GA
DIRSERVER-1083 Search on an custom attribute added to the dynamic schema fails when no result is found
  - CRITICAL
DIRSERVER-465 Make partitions nestable: remove the nexus singleton!
  - can wait
DIRSERVER-646 Replacing an unknown attribute with no values (deletion) causes an error
  - CRITICAL
DIRSERVER-1056 Cleaning the warnings
  - can wait
DIRSERVER-1064 Admin password cannot be hashed
  - this has been fixed
DIRSERVER-798 Configurable ApacheDS OSGi bundles require schema oid assignments
  - can wait
DIRSERVER-955 FilterMatch permissions are not being handled in Access Control decisions
  - need more investigation

So personally I would consider the following issues on our plate for this release:

DIRSERVER-1149 Removing a non existing value of an attribute removes one of this attribute's values
DIRSERVER-957 OOM when adding a lot of entries
DIRSERVER-832 Added Attributes are all case sensitive
DIRSERVER-956 Aborting a client search does not stop the search
DIRSERVER-990 2 objects of the Apache DS Schema share the same OID
DIRSERVER-1083 Search on an custom attribute added to the dynamic schema fails when no result is found
DIRSERVER-646 Replacing an unknown attribute with no values (deletion) causes an error

This needs more investigation:

DIRSERVER-955 FilterMatch permissions are not being handled in Access Control decisions

I think we can knock these out pretty rapidly.  If we cannot do so by Wednesday of next week I recommend we release anyway.  There's no reason why we should not.  1.5.2 is a feature introduction release that does not guarantee a bug free server.  Users would probably prefer to have a trackable release with these new features as a line in the sand to test against.

Also I want to fix the present installer situation so we have installers once again for our latest release.

Thoughts?

Alex



------=_Part_10037_20645429.1206995919709--