From: Bastien Guerry <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Josiah Schwab <jschwab@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Reuben Thomas <rrt@sc3d.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: Tue, 01 Nov 2016 16:28:36 +0100 [thread overview]
Message-ID: <87r36vb4nv.fsf@bzg.fr> (raw)
In-Reply-To: <87k2cne9ud.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 01 Nov 2016 12:08:26 +0100")
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> I thing we should automate bugfix releases with regular version
> numbering scheme, e.g., 8.3.7 release, /as a replacement for/
> org-YYYYMMDD releases.
Okay.
> Therefore:
>
> 1. org-YYYYMMDD could be renamed org-MAJOR-MINOR-BUGFIX# where MAJOR
> MINOR are never modified automatically, and BUGFIX# is (1+ last
> BUGFIX#).
I'm fine with this.
> 2. Conditions to make a new automated release ought to change. We could
> wait for a full "idle" week after a commit before releasing (IOW,
> wait for one week after a commit but every new commit during that
> period resets the counter). "next Monday" rule has bitten us already.
> The new rule is not perfect either, but is more secure. If one full
> week is too long, we may reduce it to 4 days.
I'm fine with the rule you suggest.
> OTOH "org-bugfix.tar.gz" is not monotonic, so it buys us very little.
We just need to have a link that I can put on the website without the
need to edit the website for each minor release.
Best,
--
Bastien
next prev parent reply other threads:[~2016-11-01 15:28 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
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 [this message]
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=87r36vb4nv.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=jschwab@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=rrt@sc3d.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).