[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [sbws/master] Rephrase timestamps format



commit 34e566c3ef6be9956ca20e58f010ab8c8b2a6e54
Author: juga0 <juga@xxxxxxxxxx>
Date:   Fri Sep 14 19:51:43 2018 +0000

    Rephrase timestamps format
---
 CONTRIBUTING.rst | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index b2b96eb..65a2349 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -93,6 +93,10 @@ Before release 1.0.0, some docstrigs do not have 3 double quotes ``"""``
 
 New features should add a corresponding documentation.
 
+Timestamps must be in UTC. It is prefered to use ``datetime`` objects or
+Unix timestamps. Timestamps read by the user should be always formatted in
+`ISO 8601 <https://en.wikipedia.org/wiki/ISO_8601>`_
+
 Git and GitHub Guidelines
 =========================
 
@@ -119,12 +123,6 @@ a branch, add a version suffix (for example: "_02").
 Coding Guidelines
 =================
 
-**Strongly prefer Unix timestamps or datetime objects in UTC** and always
-work in UTC for as long as possible. When reading/writing/manipulating results
-from some period of time in the past, always err on the side of caution. For
-example, open an extra file into the past just in case it happens to include
-result lines that have timestamps that are still considered valid (of course,
-ignore results in the file that are no longer valid).
 
 **Document your addition, fix, change, or whatever in the changelog**. See
 `keep a changelog`_ for the standard we follow. Of note, add Added, Changed,



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits