HI!
BTW: Happy New Year.
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
Ciao, Michael.
--On Monday, January 08, 2018 4:12 PM +0100 Michael Ströder michael@stroeder.com wrote:
HI!
BTW: Happy New Year.
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
When it's ready.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount wrote:
--On Monday, January 08, 2018 4:12 PM +0100 Michael Ströder michael@stroeder.com wrote:
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
When it's ready.
I expected this answer.
So after almost 20 years the OpenLDAP project looks pretty dead.
Ciao, Michael.
Michael Ströder wrote:
Quanah Gibson-Mount wrote:
--On Monday, January 08, 2018 4:12 PM +0100 Michael Ströder michael@stroeder.com wrote:
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
When it's ready.
I expected this answer.
So after almost 20 years the OpenLDAP project looks pretty dead.
Not quite, but it's certainly got fewer interesting problems left to solve. As an open source project it certainly could use some more community involvement. Symas Corp. has been funding all of the web/email/repo resources for the past few years, and funding nearly all of the development work too. As such most of the development activity is being discussed on Symas-specific forums.
Obviously this is non-optimal - I keep reminding people to use this mailing list to discuss issues, so that we have a permanent record of our technical decisions. But there's some friction there, since current work also revolves around customer-specific issues and we're testing with customer-specific data, which must be kept confidential.
Michael,
First, thanks for being a good friend and supporter of the Project all these years. I certainly hope this doesn’t drive you away in frustration. The better answer to the original email would have been to share our dilemma with some recent ITS’s that we want to get resolved before churning the maintenance stream. These problems occupied a significant amount of time late last year as they cropped up in real production environments and are in the way of new deployments.
Howard is right about Symas having done what it has done. We have not intentionally hidden activities away from the Project. Problems have generally been faithfully reflected in the ITS stream and certainly the code is all in the open. What appears, from the outside, as a non-optimal dominance by Symas is reflective of a non-optimal interest by “the community” in participating, in getting involved.
We have seen too many core technologies, mission-critical to the operation of the Enterprise and the Internets, languish for lack of ongoing sponsorship and “interest”. There are many reasons for this, none particularly good for the ecosystem. Symas is proud to have kept OpenLDAP moving forward in support of real world requirements … and Open Source.
With our best wishes to you and yours for 2018,
Marty Heyman +1 650 963 7606
On Jan 9, 2018, at 4:57 AM, Howard Chu hyc@symas.com wrote:
Michael Ströder wrote:
Quanah Gibson-Mount wrote:
--On Monday, January 08, 2018 4:12 PM +0100 Michael Ströder michael@stroeder.com wrote:
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
When it's ready.
I expected this answer. So after almost 20 years the OpenLDAP project looks pretty dead.
Not quite, but it's certainly got fewer interesting problems left to solve. As an open source project it certainly could use some more community involvement. Symas Corp. has been funding all of the web/email/repo resources for the past few years, and funding nearly all of the development work too. As such most of the development activity is being discussed on Symas-specific forums.
Obviously this is non-optimal - I keep reminding people to use this mailing list to discuss issues, so that we have a permanent record of our technical decisions. But there's some friction there, since current work also revolves around customer-specific issues and we're testing with customer-specific data, which must be kept confidential.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
--On Tuesday, January 09, 2018 9:57 AM +0000 Howard Chu hyc@symas.com wrote:
Obviously this is non-optimal - I keep reminding people to use this mailing list to discuss issues, so that we have a permanent record of our technical decisions. But there's some friction there, since current work also revolves around customer-specific issues and we're testing with customer-specific data, which must be kept confidential.
The answer would have been the same regardless of any of the above. We have no fixed release time table, nor should we. I'd also note that this answer is not uncommon. You'd get a similar response if you were asking other projects about when they planned to release as well.
It's also rather ironic to proclaim the project as "dead", when we've had one of the most productive periods in years. Issues that have languished in the ITS system for ages are finally being looked at and addressed. We've had significantly more traffic on the -devel list in discussion around those fixes and other issues, with my openldap-scratch repo and ITS reviews. Ondrej and others have also been noting their work and development thoughts on the -devel list (See "Approaches to ITS#8772", "VC exop and LDAPWhoAmI", "Persistent Sessionlog", etc, threads).
In addition, anyone even paying a small amount of attention to the openldap-bugs list would see there continue to be incoming issues that would need to be addressed before 2.4.46 is released (ITS#8791, is one recent example). There are also clearly commits that are currently in master only that still need review and inclusion into RE24 (ITS#8774 being one such).
As a long time participant of the list, Michael's also more then aware that the release process involves testing calls. So far, there have been zero testing calls for 2.4.46. It is not hard to deduce from the lack of said testing calls that the current code base is not considered ready for release.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
09.01.2018, 12:57, "Howard Chu" hyc@symas.com:
Michael Ströder wrote:
Quanah Gibson-Mount wrote:
--On Monday, January 08, 2018 4:12 PM +0100 Michael Ströder michael@stroeder.com wrote:
What are currently the plans for releasing 2.4.46? It's hanging in branch RE24 for quite while now.
When it's ready.
I expected this answer.
So after almost 20 years the OpenLDAP project looks pretty dead.
Not quite, but it's certainly got fewer interesting problems left to solve. As an open source project it certainly could use some more community involvement. Symas Corp. has been funding all of the web/email/repo resources for the past few years, and funding nearly all of the development work too. As such most of the development activity is being discussed on Symas-specific forums.
Hello all,
I will have some questions. for OpenLDAP next versions;
1. Docker image preparation 2. Defined as an NFV service on OpenStack 3. SDN controller compatible modularity
thinking about the working on this issue?
Regards
Ozgur
Obviously this is non-optimal - I keep reminding people to use this mailing list to discuss issues, so that we have a permanent record of our technical decisions. But there's some friction there, since current work also revolves around customer-specific issues and we're testing with customer-specific data, which must be kept confidential.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
-
Howard Chu -
Marty Heyman -
Michael Ströder -
Ozgur -
Quanah Gibson-Mount