Opened Jiras ordered by components (there may be duplicates, ie JIRA
with more than one component)
ACI: 16
AdminRole : 5
Alias : 2
ASN1 : 2
Authn: 21
Authz: 3
Avl : 2
Backend: 8
Build : 3
Cache : 0
ChangeLog : 1
ChangePwd : 0
Code quality: 12
Config: 6
Control: 13
Core: 20
Core-integ : 2
DHCP: 3
DNS : 3
Doc: 14
Extop: 2
Hash interceptor : 2
Http : 1
Index: 2
Installer : 27
Installer-plugin: 8
JDBM: 25
Replication: 26
Journal: 1
Kerberos: 3
LDAP: 20
LDIF: 2
Legal :0
Logs: 2
Mavibot: 6
Migration :0
Monitoring: 4
Network: 7
NTP: 0
OSGi: 4
PersistentSearch : 1
PPolicy: 22
Pwd Interceptor: 1
Radius: 1
Referral: 2
Replication: 26
RootDSE: 4
Schema: 21
Schema-plugin : 0
Scim: 1
Script: 1
Search : 18
Security: 3
SLP: 0
SP : 2
Test: 14
Tools : 9
TriggeInterceptor: 2
Upgrade: 6
Opened JIRAs type :
Bugs: 185
blocker : 12
critical : 21
major : 138
minor : 14
Improvements : 84
New Features : 47
Tasks/Sub-tasks : 24/1
Wishes : 8
Tests : 3
On 28/06/2019 17:56, Emmanuel Lécharny wrote:
Hi !
Just for the record and as we are on friday evening, here is the
current status of both the LDAP API and ApacheDS progress toward a
release.
- LDAP API:
a few issues have been recently fixed (4, with one waiting for the
user to aknowledge the fix), we still have 30 opened issues, 9 for
2.0.0, 5 for 2.0.0.AM5 and 5 with non affected version.
We should be good to go quickly, if needed.
- ApacheDS :
This is the big cleanup. The last version was released in August 2018,
yes, a year ago... We had 437 opened issues when the cleanup started,
we are now down to 373 (64 less !)
Many of those issues are either for newer versions or not yet
attributed to a version :
No version : 162 issues
2.1.1 : 7 issues
2.1.0 : 67 issues
2.0.0 : 9 issues
2.0.0-RC2 : 11 issues
2.0.0-RC1 : 91 issues
2.0.0.AM26 : 20 issues
Old versions : 6 issues
I'm currently reviewing all those issues, adding the right component
to them. The idea is to go on and fix a set of issues for a given
component, as it's easier to do that when you have many, you are in
the code area and you don't have to switch to something else.
However, I don't think we will be able to fix all those issues, so
don't expect that process will last for weeks and weeks. The idea is
to stabilize the server, make it so it can be integrated in Studio
(this is currently the case, AFAICT, thanks to Stefan hard works !)
and to cut a release. We will fix group of other issues later in a
coming release (I expect that it won't take another year though).
- Studio :
I don't have a lot to say about Studio, except that it now builds and
run with the LDAP API and ApacheDS trunk version. We have to thank
Stefan for that !
A special thank to Colm who joined us in this effort !
Have a good week-end !
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
