increment version number

jpjones76 · Mar 3, 2020 · 122783a · 122783a · jpjones76 · Mar 3, 2020
1 parent 1cf87b5
commit 122783a
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/Project.toml b/Project.toml
@@ -1,7 +1,7 @@
 name = "SeisIO"
 uuid = "b372bb87-02dd-52bb-bcf6-c30dd83fd342"
 authors = ["Joshua Jones <highly.creative.pseudonym@gmail.com>"]
-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
@@ -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
@@ -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".