# Release plans / back porting ? (Peter Danecek)

**URL:** https://discourse.obspy.org/t/release-plans-back-porting-peter-danecek/191
**Category:** Users Mailing List Archive
**Tags:** archive
**Created:** [June 6, 2013, 2:26pm UTC](https://discourse.obspy.org/t/release-plans-back-porting-peter-danecek/191 "2013-06-06T14:26:05Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Claudio\_Satriano](https://discourse.obspy.org/letter_avatar_proxy/v4/letter/c/48db29/32.png) [@Claudio\_Satriano](https://discourse.obspy.org/u/Claudio_Satriano)
#### Post date: [June 6, 2013, 2:26pm UTC](https://discourse.obspy.org/t/release-plans-back-porting-peter-danecek/191/1 "2013-06-06T14:26:05Z")

</div>

Hi Peter,  
you could have a look at the [issues filed after 2012-12-17](https://github.com/obspy/obspy/search?p=1&q=created:%3E2012-12-17&type=Issues) (release date of 0.8.3) to see what happened since then.

This can maybe help you in your decision.

Anyhow, my experience is that you cannot be cutting edge on just a few pieces of your setup (like using python 2.7.5), without having the latest versions of all the remaining tools/libraries.

So, if you decide to stick on 0.8.3, my advice would be to stay with python 2.7.3, since 0.8.3 has been thoroughly tested on that version.  
Maybe back porting 342d86f is fine, but there might be other quirks which are yet to be found out.

Let me know  
Claudio

---

<div class="post-metadata">

### Author: ![Claudio\_Satriano](https://discourse.obspy.org/letter_avatar_proxy/v4/letter/c/48db29/32.png) [@Claudio\_Satriano](https://discourse.obspy.org/u/Claudio_Satriano)
#### Post date: [June 6, 2013, 2:27pm UTC](https://discourse.obspy.org/t/release-plans-back-porting-peter-danecek/191/2 "2013-06-06T14:27:39Z")

</div>

Ops, I just realized that the link does not show up on the web.  
Here it is:

issues filed after 2012-12-17:

[https://github.com/obspy/obspy/search?p=1&q=created:%3E2012-12-17&type=Issues](https://github.com/obspy/obspy/search?p=1&q=created:%3E2012-12-17&type=Issues)

Claudio
