On Wed, 2017-02-15 at 08:43 +1000, William Brown wrote:
On Tue, 2017-02-14 at 18:20 +0000, Ric wrote:
> Hi All,
> I am aware that RHDS9 goes EoL in March. As I understand it, 389 is
> effectively upstream of RHDS and thus not directly affected.
> However, is there a similar roadmap for 389 please? i.e. is there a
> forecast time when yum-upgrade will no longer get the latest patches and
> fixes for 389 and a new install/upgrade/migration will be required?
RHDS9 correlates to the 389-ds-base 1.2.x series. RHDS10 correlates to
the 389-ds-base 1.3.x series.
We do try to keep the 389-ds-base release dates in-sync with Red Hat's
schedules, but we are unable to disclose what those schedules are
publicly. Sorry! For your purposes, assume that when RHDS9 is EOL, that
389-ds-base 1.2.x will be also (sorry, but we don't really have a lot of
investment in maintaining older code bases once they go EOL in RH :( ).
For you, you may find that the best course of action is to prepare to
upgrade and migrate to 1.3.x (RHDS10). If you are a supported RHEL
customer, please contact GSS about this procedure. You can do this
through your RH account.
If you are not a customer, you can choose to upgrade to CentOS7 or EL7
equivalent and use the 389-ds-base package that is supported.
The upgrade should be very straightforward, so I hope that this helps
As a follow up, here are our public product support dates.
Directory Server 9 according to this page states:
Maintenance support: Jun 10, 2015 – Jun 10, 2017
It is likely that as an upstream project, on this date we will cease
1.2.x support. Please contact your RH account representative for more
Red Hat, Brisbane