From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 22687@debbugs.gnu.org
Subject: bug#22687: Online manual not updated automatically
Date: Tue, 16 Feb 2016 17:25:04 +0100 [thread overview]
Message-ID: <20160216162504.GC5914@solar> (raw)
In-Reply-To: <idj4md96kb3.fsf@bimsb-sys02.mdc-berlin.net>
On Tue, Feb 16, 2016 at 11:06:40AM +0100, Ricardo Wurmus wrote:
> Many other projects publish online manuals for both stable and
> development versions. As our releases are a little far apart and we’re
> encouraging to do “guix pull” (so users really run the development
> version) I think it would indeed make sense to also publish an
> up-to-date version of the manual along with the manual for the latest
> release.
Or alternatively, release more often :-)
I wonder whether we should not make a point release after each security
update instead of encouraging people to use "guix pull" (but we would
quickly arrive at 0.9.9 now, after which only 1.0.0 would be a reasonable
option to keep numerical and lexicographical ordering consistent).
Or a point-point release as 0.9.0.1 and so on.
Andreas
next prev parent reply other threads:[~2016-02-16 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 21:50 bug#22687: Online manual not updated automatically Leo Famulari
2016-02-15 22:49 ` Thompson, David
2016-02-16 10:06 ` Ricardo Wurmus
2016-02-16 16:25 ` Andreas Enge [this message]
2016-02-16 16:33 ` Ricardo Wurmus
2016-02-16 16:42 ` Andreas Enge
2016-02-16 17:14 ` Florian Paul Schmidt
2016-02-16 20:37 ` Mathieu Lirzin
2016-02-21 22:41 ` Ludovic Courtès
2016-02-17 4:07 ` Chris Marusich
2016-02-18 9:38 ` Alex Kost
2016-02-21 22:43 ` Ludovic Courtès
2018-12-17 10:52 ` Julien Lepiller
2018-12-17 11:28 ` Ricardo Wurmus
2019-07-31 15:31 ` Julien Lepiller
2019-07-31 17:46 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160216162504.GC5914@solar \
--to=andreas@enge.fr \
--cc=22687@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.