unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Please write "Update to <version>" instead of "Update snapshot"
Date: Sat, 25 Nov 2017 19:43:11 -0500	[thread overview]
Message-ID: <87d145vpi8.fsf@netris.org> (raw)

Hello Guix,

I'd like to propose that we deprecate the practice of simply writing
"Update snapshot" in the summary line of software updates, and instead
consistently write "Update to <version>", as we do for the vast majority
of updates.

This practice seems to have originated with our 'guix-devel' package,
and iirc for a long time that was the sole exception to our usual
convention.  However, recently I've seen this practice gradually
spreading to other packages, e.g. gcl, kodi, xf86-video-intel, cuirass,
guile2.2-ssh, etc.  I've CC'd the few Guix developers who have started
doing this.

In my opinion, the version number is a very useful piece of information
to see for update commits when browsing the commit history.  I regard
the practice of omitting the version number to be a slowly creeping
regression in our otherwise exceptionally good conventions for commit
logs.  I humbly propose that we nip this regression in the bud.

What do you think?

      Mark

             reply	other threads:[~2017-11-26  0:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26  0:43 Mark H Weaver [this message]
2017-11-26 19:03 ` Please write "Update to <version>" instead of "Update snapshot" Leo Famulari
2017-11-26 22:09   ` Ludovic Courtès
     [not found] <20171109014628.6934.66587@vcs0.savannah.gnu.org>
     [not found] ` <20171109014630.1CC31201B8@vcs0.savannah.gnu.org>
2017-11-13  4:14   ` 01/01: gnu: totem: Enable parallel build Mark H Weaver
2017-11-13 12:49     ` Kei Kebreau
2017-11-26  1:21       ` Please write "Update to <version>" instead of "Update snapshot" Kei Kebreau

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d145vpi8.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).