Hello again after this too long break. Well, I wasn’t on vacation the whole time, but I find it hard to go back into writing mood. I also got distracted by the amount of snow that we received in Grenoble’s valley: yesterday there was still 30 cm of snow everywhere around my house.
Anyway, I’m back to this blogosphere, with the same hope that I will be posting more regularly than last year.
Looking back at 2009, it’s been an amazing year for the OpenDS project team.
In a year, we’ve released 3 important versions of OpenDS, with many features and innovation:
- In January, OpenDS 1.2 added the Control Panel, SASL security, Support for JCEKS, enhancements in Access Controls and several Solaris / OpenSolaris specific features such as IPS packages, support for SMF and RBAC, …
- In July, OpenDS 2.0 brought many performance improvements, several new features including Assured Replication, Recurring Tasks, Locale specific matching rules, and enhancements of the monitoring, the indexing, the ease of use, …
- In December, OpenDS 2.2 added support for Fractional Replication, External Changelog, some date and time based matching rules, syntaxes extensions for Enumerations and Regular Expressions, up to 8 Masters in Replication, …
During the same period, the OpenDS Community has more than doubled, and so has the number of downloads of the OpenDS builds.
The OpenDS development continues. We have planned the release of OpenDS 2.4 in the middle of 2010. You can check the OpenDS RoadMap to see the features that are being worked on. If you’re using OpenDS in production, or if you’re building solutions that use the OpenDS LDAP directory server, please share your experience with the community. Send us details of your experiences or deployments. We will post them on the OpenDS wiki or Sun Adoption Stories blog.
While we’re still in January, let me wish all of you a happy and prosperous New Year 2010, and a long life to the OpenDS project.
Technorati Tags: directory-server, java, ldap, opends, opensource, Sun
Comments are disabled on the other post, but wanted to point out that numsubordinates does not provide the number of entries under a branch. In general it provides the number of entries one level under a branch. These can be very different numbers.
Thanks Frank. You’re correct, numSubordinates indicate the number of immediate child entries under a node in the DIT.