# Rasa Open Source 2.0 is out now!

**URL:** <https://forum.rasa.com/t/rasa-open-source-2-0-is-out-now/35577>\
**Category:** Important Updates\
**Created:** [October 7, 2020, 11:54am UTC](https://forum.rasa.com/t/rasa-open-source-2-0-is-out-now/35577 "2020-10-07T11:54:08Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![petasis](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@petasis](https://forum.rasa.com/u/petasis)\
**Post date:** [October 12, 2020, 1:33pm UTC](https://forum.rasa.com/t/rasa-open-source-2-0-is-out-now/35577/29 "2020-10-12T13:33:41Z")

</div>

I am using rasa/sdk 2.0. In rasa 2.0.0rc4 I had a workarround. In rasa 2.0 I don’t know what to do. The domain is included in the archive.

When you mention the “The `flight_departure_form` should come before the slot events”, in which file you are referring to? Can you send me a “corrected” story? (I generated the stories with `rasa interactive`).

```
rasa --version
Rasa Version : 2.0.0
Rasa SDK Version : 2.0.0
Rasa X Version : None
Python Version : 3.8.5 (default, Aug 12 2020, 00:00:00) 
Operating System : Linux-5.8.12-200.fc32.x86_64-x86_64-with-glibc2.2.5
Python Path : /usr/bin/python3

```

Regarding running the form, no, no form slots are filled before calling the form activation/validation.

---

_[View the full topic](https://forum.rasa.com/t/rasa-open-source-2-0-is-out-now/35577)._