[389-users] 1.2.11.30 ETA?

[Rich Megginson]

On 07/03/2014 03:58 PM, Timothy Pollard wrote:
> On Thu, 03 Jul 2014 07:27:51 -0600
> Rich Megginson <rmeggins at redhat.com> wrote:
>> On 07/02/2014 08:13 PM, Timothy Pollard wrote:
>>> I'd also like to know if anyone has anything specific they could share about
>>> the intended release date of 1.2.11.30. I understand that it's a case of
>>> "When It's Ready", but I was hoping to know if the fact that all the
>>> tickets in the Trac milestone for it are closed now indicates that "When
>>> It's Ready" will be soon. :-)
>> It depends on what platform you are on.
>>
>> If you are on RHEL6, your best bet is to just use the 389-ds-base package
>> that comes with the base OS.  The copr/fedorapeople repos are only used if
>> you require to be on the "bleeding" edge and cannot or do not want to wait
>> for your particular bug/feature to show up in the 389-ds-base package in the
>> base OS.
>>
>> If you are on RHEL5, then we'll see what we can do.
> We're actually on CentOS 6. We'd be happy to use the standard distro version,
> but we're seeing a lot of crashes (about half a dozen or so a day; we've got
> Puppet set up to check every five minutes and restart if it's down). We're not
> absolutely sure that our problems are caused by the bugs fixed in 1.2.11.30,
> but we want to try rolling out the fixes as soon as possible to see if it
> alleviates the problems.

Would you be willing to build from source?

>>> I'm specifically asking because we have been seeing a lot of crashes on our
>>> LDAP system. The coredumps we sent through resulted in some tickets that
>>> have been fixed as part of 1.2.11.30, so we're hoping that the upgrade
>>> would make our systems more stable.
>> Which tickets are these?
> https://fedorahosted.org/389/ticket/47696 is the ticket I reported, but nhosoi
> created https://fedorahosted.org/389/ticket/47750 as a related ticket, and
> https://fedorahosted.org/389/ticket/47764 seems to be affecting us as well.

Looks like these are due for RHEL 6.6 . . .

>
> Thanks,