# Ray 1.x \<- 2.2 backwards compatibility

**URL:** https://discuss.ray.io/t/ray-1-x-2-2-backwards-compatibility/9193
**Category:** RLlib
**Created:** [February 1, 2023, 5:54pm UTC](https://discuss.ray.io/t/ray-1-x-2-2-backwards-compatibility/9193 "2023-02-01T17:54:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![fst](https://avatars.discourse-cdn.com/v4/letter/f/c0e974/32.png) [@fst](https://discuss.ray.io/u/fst)
#### Post date: [February 1, 2023, 5:54pm UTC](https://discuss.ray.io/t/ray-1-x-2-2-backwards-compatibility/9193/1 "2023-02-01T17:54:03Z")

</div>

Hi!

we are considering to update from ray 1.x to 2.2 for out internal collection of policy algorithms and environments, so we can use the new interface for upcoming algorithms (and we can slowly migrate existing ones one by one as the opportunity arises).  
I found [this](https://docs.google.com/document/d/1a3UEHEz6_Jth9O_2GR9Qp9c9IFyD5dObHCNSBsRgPGU/edit#) migration guide that mentions " Don’t worry, your old code will still be supported for a long time (probably throughout all of Ray 2.x). However, at some point, RLlib will fully deprecate the execution plan API."

We are e.g. using ParallelRollouts in our existing policy implementations. On first sight this class was completely removed in ray 2.2.0 now?

So was backwards compatibility dropped in 2.2 and we would have to migrate each and every agent and environment in one go to the new approaches in order to update to the new version?

Or should we perhaps update to the last backwards compatible version (looks like this was 2.1?) which already hase (some) of the new interfaces also and stay at this version until all the legacy code is migrated?

Thanks in advance for any proposals! 🙂

---

<div class="post-metadata">

### Author: ![arturn](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/arturn/32/2096_2.png) [@arturn](https://discuss.ray.io/u/arturn)
#### Post date: [April 14, 2023, 12:01am UTC](https://discuss.ray.io/t/ray-1-x-2-2-backwards-compatibility/9193/2 "2023-04-14T00:01:43Z")

</div>

There exists a general Ray 2.0 migration guide:

> **[Ray 2.0 Migration Guide](https://docs.google.com/document/d/12ODPbhEzeyDRUt8ehHDiKCFoxksPWJOUNEicGhNxtRg/edit)**
>
> Migration Guide for Ray 2.0 This document provides guidance for Ray users to upgrade to 2.0. If you have any questions, please contact the team on Discourse. Core APIs Ray Core - Library APIs Ray RLlib - Ray Tune - Ray Train - Ray Serve - ...

---

<div class="post-metadata">

### Author: ![arturn](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/arturn/32/2096_2.png) [@arturn](https://discuss.ray.io/u/arturn)
#### Post date: [April 14, 2023, 12:02am UTC](https://discuss.ray.io/t/ray-1-x-2-2-backwards-compatibility/9193/3 "2023-04-14T00:02:24Z")

</div>

If you have any specific questions when it comes to migration, feel free to ask them here.  
I’d recommend upgrading to the newest version or Ray right away to save some time.
