[taler-docs] branch master updated: DD37: document future 'revive' option

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 037996ce DD37: document future 'revive' option
037996ce is described below

commit 037996cee61d3968d7c8cd58b4ecce82e9b757a1
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Jun 5 11:22:22 2023 +0200

    DD37: document future 'revive' option
---
 design-documents/037-wallet-transactions-lifecycle.rst | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/design-documents/037-wallet-transactions-lifecycle.rst 
b/design-documents/037-wallet-transactions-lifecycle.rst
index d2e9b04c..9d95379c 100644
--- a/design-documents/037-wallet-transactions-lifecycle.rst
+++ b/design-documents/037-wallet-transactions-lifecycle.rst
@@ -1089,9 +1089,6 @@ Alternatives
   not ask again."). Probably at best a post-1.0 feature.
 
 
-Drawbacks
-=========
-
 Discussion / Q&A
 ================
 
@@ -1099,7 +1096,11 @@ Discussion / Q&A
   has created the transaction.  It is possible that network requests
   are happening before that, but they are not considered to be part
   of the transaction.
-* We have decided against a `cancel` state, because it resulted
-  in too much complexity.  Instead of doing a direct `cancel`,
+* We have decided against a ``cancel`` state, because it resulted
+  in too much complexity.  Instead of doing a direct ``cancel``,
   the user has to go to the transaction and abort and/or delete
   it.
+* We might add a ``revive`` action in the future that allows
+  to go from ``aborting`` back to ``pending`` for transactions
+  where this makes sense.  We're not doing it right now
+  to simplify things.
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.