# 1.2.0 past due

**URL:** <https://bisq.community/t/1-2-0-past-due/7866>\
**Category:** Development\
**Created:** [June 15, 2019, 3:45pm UTC](https://bisq.community/t/1-2-0-past-due/7866 "2019-06-15T15:45:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![goraelec](https://bisq.community/letter_avatar/goraelec/32/6_22734026db12803ebb3e059622ac3534.png) [@goraelec](https://bisq.community/u/goraelec)\
**Post date:** [June 15, 2019, 3:45pm UTC](https://bisq.community/t/1-2-0-past-due/7866/1 "2019-06-15T15:45:36Z")

</div>

Can’t help but notice that [https://github.com/bisq-network/bisq/milestone/30](https://github.com/bisq-network/bisq/milestone/30) is showing up as being past due by 16 days with the latest update happening a month ago. I understand the nature of open-source development and in such projects as Bisq it is almost impossible to set any deadlines, but it’s kind of alarming to see this delay.

Is there a reason for this happening? What can I or the community do to help?

---

<div class="post-metadata">

**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/6_22734026db12803ebb3e059622ac3534.png) [@Homard](https://bisq.community/u/Homard)\
**Post date:** [June 15, 2019, 4:45pm UTC](https://bisq.community/t/1-2-0-past-due/7866/2 "2019-06-15T16:45:20Z")

</div>

The roadmap is here [https://bisq.network/roadmap/](https://bisq.network/roadmap/)  
You can see that last release was just 2 weeks ago.  
And the rythm was very fast before.  
For my part I think that the devs are also allowed from time to time to breath a bit.

If you are a dev, browse the github, there is much to do.

---

<div class="post-metadata">

**Author:** ![goraelec](https://bisq.community/letter_avatar/goraelec/32/6_22734026db12803ebb3e059622ac3534.png) [@goraelec](https://bisq.community/u/goraelec)\
**Post date:** [June 15, 2019, 8:05pm UTC](https://bisq.community/t/1-2-0-past-due/7866/3 "2019-06-15T20:05:04Z")

</div>

I wish I could help, but I’m not a dev (yet)
