From 122783a6f2a50932a8e5468b73211d8ab26611ae Mon Sep 17 00:00:00 2001 From: Joshua Date: Mon, 2 Mar 2020 23:51:52 -0800 Subject: [PATCH] increment version number --- Project.toml | 2 +- docs/conf.py | 4 ++-- docs/src/Formats/timeseries.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Project.toml b/Project.toml index 2f8c4074..3540021a 100644 --- a/Project.toml +++ b/Project.toml @@ -1,7 +1,7 @@ name = "SeisIO" uuid = "b372bb87-02dd-52bb-bcf6-c30dd83fd342" authors = ["Joshua Jones "] -version = "0.4.1" +version = "1.0.0" [deps] Blosc = "a74b3585-a348-5f62-a45c-50e91977d574" diff --git a/docs/conf.py b/docs/conf.py index 153a4431..0ad6f148 100755 --- a/docs/conf.py +++ b/docs/conf.py @@ -59,9 +59,9 @@ # built documents. # # The short X.Y version. -version = u'0.4.1' +version = u'1.0.0' # The full version, including alpha/beta/rc tags. -release = u'0.4.1' +release = u'1.0.0' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/docs/src/Formats/timeseries.rst b/docs/src/Formats/timeseries.rst index c2fb1528..b2914d7d 100644 --- a/docs/src/Formats/timeseries.rst +++ b/docs/src/Formats/timeseries.rst @@ -131,7 +131,7 @@ Examples Memory Mapping ============== -`memmap=true` is considered unsafe because Julia language handling of SIGBUS/SIGSEGV and associated risks is undocumented as of SeisIO v0.4.1. Thus, for example, we don't know what a connection failure during memory-mapped file I/O does. In some languages, this situation without additional signal handling was notorious for corrupting files. +`memmap=true` is considered unsafe because Julia language handling of SIGBUS/SIGSEGV and associated risks is undocumented as of SeisIO v1.0.0. Thus, for example, we don't know what a connection failure during memory-mapped file I/O does. In some languages, this situation without additional signal handling was notorious for corrupting files. **Under no circumstances** should `mmap=true` be used to read files directly from a drive whose host device power management is independent of the destination computer's. This includes all work flows that involve reading files directly into memory from a connected data logger. It is *not* a sufficient workaround to set a data logger to "always on".