[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Taler] (docs) installation
From: |
Thien-Thi Nguyen |
Subject: |
Re: [Taler] (docs) installation |
Date: |
Fri, 04 Dec 2020 01:42:57 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
() Christian Grothoff <grothoff@gnunet.org>
() Thu, 3 Dec 2020 11:46:42 +0100
> Which one is the best choice? Or am i missing something?
For the "internal" dependencies in the manual(s), I think it
would be good to document the general rule (0.x depends on
0.x) instead of specific versions (0.8 depends on 0.8), so
that we don't need to change the text for every release. Only
in the release notes / release announcement I would give the
super-specific details (like if a merchant backend 0.13.4
unusually requires exchange 0.13.2 and not just any 0.13.*).
> I wonder why merchant 0.8.0 has a Git
> tag (v0.8.0) but no released tarball...
That is indeed a bit strange, my upload must have failed and
I didn't notice yet. Alas, we're still in the process of
getting all components ready for the v0.8-release, and so the
'final' release checks (like: did the uploads work) have not
yet been done ;-).
Thanks for the clarification. I've revised the text to explain
the rule (and the possible exception) and to only give specific
version numbers for GNU Taler as an example.
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query) ; (2020) Software Libero
(pcase (context query) ; = Dissenso Etico
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
signature.asc
Description: PGP signature