# Any schedule for 1.0.2

**URL:** <https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [July 10, 2017, 8:31am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429 "2017-07-10T08:31:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\
**Post date:** [July 10, 2017, 8:31am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/1 "2017-07-10T08:31:42Z")

</div>

Hi ECE.

We worry about for 1.0.1 ECE we installed, we can not upgrade to 1.0.2. So we are waiting for 1.0.2 to be released then to use in production service. Is there any ETA for that?

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [July 10, 2017, 11:20am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/2 "2017-07-10T11:20:08Z")

</div>

Hello,

I''m afraid we don't publish ETAs got specific versions. Sorry.

Cheers

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [July 10, 2017, 3:38pm UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/3 "2017-07-10T15:38:13Z")

</div>

@weibin.wu in fact the blocking issue on the release of 1.0.2 (and its primary feature!) is the ability to upgrade from 1.0.1 - so you should have no concerns on deploying 1.0.1 on that score

Alex

---

<div class="post-metadata">

**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\
**Post date:** [July 11, 2017, 2:40am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/4 "2017-07-11T02:40:54Z")

</div>

@Alex_Piggott, so the upgrade function is on 1.0.2 version. And the feature can help 1.0.1 users to upgrade to 1.0.2 right?

So it does not matter whether users are using 1.0.0 or 1.0.1.

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [July 11, 2017, 3:38am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/5 "2017-07-11T03:38:51Z")

</div>

@weibin.wu

> the upgrade function is on 1.0.2 version. And the feature can help 1.0.1 users to upgrade to 1.0.2 right?

That is correct, a 1.0.0 or 1.0.1 user will be able to run a script (similar to the install script) to upgrade to 1.0.2 once it is released. The upgrade should not be interruptive to running Elasticsearch clusters.

> So it does not matter whether users are using 1.0.0 or 1.0.1.

This is correct (literally the only difference between 1.0.0 and 1.01 is that the former ships with Elasticsearch 5.4.0 and the latter with 5.4.1)

Alex

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 25, 2017, 3:38am UTC](https://discuss.elastic.co/t/any-schedule-for-1-0-2/92429/6 "2017-07-25T03:38:51Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.