My official +1 vote.


On 03/08/2024 17:12, Shawn McKinney wrote:


On Aug 2, 2024, at 11:19 AM, Emmanuel Lecharny <[email protected]> wrote:

Hi all,

this is a vote for the release of Apache LDAP API 2.1.7

This release is fixing a few issues and add a new control:

* https://issues.apache.org/jira/browse/DIRAPI-394 Add support for
control 1.3.6.1.4.1.30221.2.5.44 (Naming Entries With entryUUID)
* https://issues.apache.org/jira/browse/DIRAPI-398 Release Pooled LDAP
Connections when closed
* https://issues.apache.org/jira/browse/DIRAPI-400 Hang in LDAP URL parser
* https://issues.apache.org/jira/browse/DIRAPI-401 Unhandled Exception
(NegativeArraySizeException) in Asn1Decoder
* https://issues.apache.org/jira/browse/DIRAPI-402 unhandled exception
(ArrayIndexOutOfBoundsException) in LDAP URL parser
* https://issues.apache.org/jira/browse/DIRAPI-403 OutOfMemory error
in Asn1Decoder for LDAP messages
* https://issues.apache.org/jira/browse/DIRAPI-404 An inefficient constructor
* https://issues.apache.org/jira/browse/DIRAPI-405 A possible handle leak

The revision :

https://github.com/apache/directory-ldap-api/tree/d57c39c7883ad554eef1bba1eee55cdd008775e3


The source and binary distribution packages:
https://dist.apache.org/repos/dist/dev/directory/api/2.1.7

The staging repository:
https://repository.apache.org/content/repositories/orgapachedirectory-1232


Please cast your votes:
[ ] +1 Release Apache LDAP API 2.1.7
[ ] 0 abstain
[ ] -1 Do not release Apache LDAP API 2.1.7


+ 1. Checked out (by tag) built, ran tests. Also ran fortress integration tests 
against it.

Looks good!

—
Shawn


Thanks !

--
Regards,
Cordialement,
Emmanuel Lécharny


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


--
*Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to