emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]
Date: Mon, 31 Oct 2016 20:06:18 +0100	[thread overview]
Message-ID: <871sywfidx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877f8otkou.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 31 Oct 2016 19:52:49 +0100")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> Nicolas Goaziou writes:
>> However, I think we should make more frequent bugfix releases. We may
>> even automate such releases, e.g., one week after the last unreleased
>> bugfix in the branch. I don't do releases however, so this may just be
>> a weird idea.
>
> We already have that, it's the Org package on GNU ELPA.  There's a new
> release each monday, fully automated.

This is not exactly what I'm suggesting, although the mechanism involved
is probably the same.

I'm suggesting to do a "real release", i.e., with a reassuring version
number (Org 8.3.7, Org 8.3.8). 

Also, the rule I suggest is different: "one week after last unreleased
bugfix" vs "next monday after first unreleased bugfix". One major issue
with the current rule is, e.g., when you introduce a toxic bugfix on
a gloomy Sunday.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2016-10-31 19:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 22:30 Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)] Reuben Thomas
2016-10-30 23:57 ` Josiah Schwab
2016-10-31 11:44   ` Reuben Thomas
2016-10-31 14:56     ` Nicolas Goaziou
2016-10-31 18:52       ` Achim Gratz
2016-10-31 19:06         ` Nicolas Goaziou [this message]
2016-10-31 19:45       ` Reuben Thomas
2016-11-01 10:32         ` Bastien Guerry
2016-11-01 10:59           ` Reuben Thomas
2016-11-01 17:01             ` Bastien Guerry
2016-11-01 23:01               ` Reuben Thomas
2016-11-02  8:18                 ` Bastien Guerry
2016-11-01 10:27       ` Bastien Guerry
2016-11-01 11:08         ` Nicolas Goaziou
2016-11-01 15:28           ` Bastien Guerry
2016-11-01 17:33           ` Achim Gratz
2016-11-01 23:43             ` Nicolas Goaziou

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=871sywfidx.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=Stromeko@nexgo.de \
    --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

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).