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?
Many thanks.
Regards, Ric.
I don't see 389 server going any where because it's at the core of other Red Hat supported project's which are built on it. RHDS 9 is EOL in favor of 10 which is just built on a newer version of 389 server on RHEL 7 as opposed to 6. Upgrades between versions of 389 server are pretty transparent so the real question is when will the distribution you are using stop publishing updates for it on the version of the distribution you are running.
Original Message From:rh-389-users@vorticity.org Sent:February 14, 2017 2:21 PM To:389-users@lists.fedoraproject.org Reply-to:389-users@lists.fedoraproject.org Subject:[389-users] 389 Roadmap?
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?
Many thanks.
Regards, Ric. _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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?
Hi there,
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 you.
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?
Hi there,
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 you.
As a follow up, here are our public product support dates.
https://access.redhat.com/support/policy/updates/directory/
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 information.
On 15/02/17 05:03, William Brown wrote:
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?
Hi there,
RHDS9 correlates to the 389-ds-base 1.2.x series. RHDS10 correlates to the 389-ds-base 1.3.x series.
Ideal, thanks.
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 :( ).
Yes, I quite understand. Maintenance updates for 5 years isn't too shabby :)
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
Will do. That's my next step now I'm clear. I'll try out the two methods described in the docs.
As a follow up, here are our public product support dates.
https://access.redhat.com/support/policy/updates/directory/
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 information.
Thanks for all that William.
I'll get to work :)
cheers. Ric.
389-users@lists.fedoraproject.org
-
Paul Robert Marino -
Ric -
William Brown