2007 Report #2

[Emmanuel Lecharny <el...@gmail.com>]

2007 Report #2
----------------------

We have made some progress since last week. 4 bugs have been fixed, 2 of
thems were very dangerous.

Bugs : 29 (was 33)
Improvments : 47 (no change)
New features : 82 (no change)
Sub task : 1 (no change)
Tasks : 18 (no change)
Wishes : 6 (no change)

Let's focus on bugs. Out of those 33 bugs, we have :
2 blockers (- 1 )
0 critical (-1)
19 majors (-1)
8 minors (-1)
1 trivial

Here are the blockers :
DIRSERVER-782 : (1.0.0) Restart required after changing password
DIRSERVER-778 : (1.5.0) Entries cannot be named when mitosis is enabled.

The majors :
DIRSERVER-792 : (1.0.0) jpegPhoto attribute is returned as a String by
SearchResultEntry
DIRSERVER-787 : (1.0.0) ApacheDS tools should use the daemon classloader
infrastructure to include jars in lib/
DIRSERVER-784 : (1.0.0) The server fails to handle subtree refinement
membership references in entries upon object class changes
DIRSERVER-776 : (1.5.0) entryUUID only created when entries are added with
Mitosis enabled
DIRSERVER-770 : (1.0.0) LDIF file import at startup fails
DIRSERVER-768 : (1.0.0) provide debug output in org.apache.directory.server
.core.authn.AuthenticationService.checkAuthenticated()
DIRSERVER-766 : (1.0.0) uniqueMember attribute compare does not seem to work
properly (uniqueMemberMatch is not implemented?)
DIRSERVER-759 : (1.0.0) object scope search on non-existant DN gives
IllegalArgumentException: "Argument 'an_obj1' is null"
DIRSERVER-756 : (1.0.0) Problem with escaped comma in DN
DIRSERVER-755 : ( 1.0.0) Referrals returned as regular entries after server
restart
DIRSERVER-730 : (1.0.0) init script fails due to missing commands "success"
and "failure"
DIRSERVER-682 : (1.0.0) apacheds dump command - hangs very frequently
DIRSERVER-169 : (1.0.0) Incorrect SearchResult name and "compare" failure
using CoreContextFactory
DIRSERVER-110 : (1.0.0) Allow administrators to change and set passwords for
users

Some comments :
- DIRSERVER-788 should be investigated. It's not really a bug per se, but
this is annoying.
- DIRSERVER-770 needs to be investigated on a Windows(TM) machine. Anyone ?
- DIRSERVER-768 is pretty much an improvment, not a bug.
- DIRSERVER-759 has been tested against 1.5.0, but I'm pretty sure that we
have the very same problem with 1.0.0
- DIRSERVER-682 is it still an issue? It was created against ADS 1.0 RC3 ...
- DIRSERVER-169 is in the field for almost one year now...

If I just select the 1.0 relative bugs, and remove the dubious bugs ( 768
and 682), we have 16 major, critical or blocking bugs.

It would be cool if you vote for the most important issues, so we can focus
on them. At the end, we will fix all of them, so you might think that the
fix order is not important, but it is...

Emmanuel.

-- 
Cordialement,
Emmanuel Lécharny
www.iktek.com