emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julian Bean <jules@jellybean.co.uk>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode release 7.8.11
Date: Tue, 29 May 2012 11:55:21 +0100	[thread overview]
Message-ID: <F5781320-EAD9-4CBE-9D77-26DC57CAF774@jellybean.co.uk> (raw)
In-Reply-To: <87hauzpazp.fsf@altern.org>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]


On 29 May 2012, at 10:55, Bastien wrote:
> 
> ~$ git log release_7.8.03..release_7.8.11
> 
> will display the git logs between those two releases.

Thanks. I will find myself a git checkout and take a look.

> 
> The purpose of http://orgmode.org/Change.html is to contain a
> human-readable log for major releases -- the logs for the development
> version are not completely written (they are in development too).

This is reasonable.

Do I take it then that releases like 7.8.x are development releases?

As a counter-argument, I remark that if 7.8 contains bugs (I believe it does?) and you have release bug fix releases in the 7.8.x series then "normal users" might reasonably want to install them, and might reasonably want to understand what bugs are fixed. ("normal users" I guess would not necessarily have a git checkout handy to run diffs on)

Of course I recognise that organising changelogs is time consuming task and the org development team are busy people.

Jules


[-- Attachment #2: Type: text/html, Size: 1494 bytes --]

      reply	other threads:[~2012-05-29 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25  7:51 Org-mode release 7.8.11 Bastien
2012-05-25  8:58 ` Rainer Stengele
2012-05-25 21:15   ` Bastien
2012-05-29  9:08 ` Julian Bean
2012-05-29  9:22   ` Jambunathan K
2012-05-29  9:55   ` Bastien
2012-05-29 10:55     ` Julian Bean [this message]

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://www.orgmode.org/

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

  git send-email \
    --in-reply-to=F5781320-EAD9-4CBE-9D77-26DC57CAF774@jellybean.co.uk \
    --to=jules@jellybean.co.uk \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@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/emacs/org-mode.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).