From: Achim Gratz <Stromeko@nexgo.de>
To: 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: Tue, 01 Nov 2016 18:33:23 +0100 [thread overview]
Message-ID: <87r36v85r0.fsf@Rainer.invalid> (raw)
In-Reply-To: 87k2cne9ud.fsf@nicolasgoaziou.fr
Nicolas Goaziou writes:
> This is not what I'm suggesting. Let me try to expunge a bit.
>
> 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. Therefore:
No, we shouldn't. It's either automatic or a release, it can't be both.
Also, the releases are distinct from the ELPA packages and you seem to
mix up the two. They are not the same thing.
> 1. org-YYYYMMDD could be renamed org-MAJOR-MINOR-BUGFIX# where MAJOR
> MINOR are never modified automatically, and BUGFIX# is (1+ last
> BUGFIX#).
Org's ELPA package has its own versioning scheme and unless package.el
grows some functionality to sanely deal with discontinuities in
versioning, we need to stick to it.
> 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.
Again, if you talk about releases, the way to do that is to tag what
should be released, preferrably sign the tag as well. Whether you roll
the release automatically or script up somthing that picks up new tags
and does it for you is a separate issue.
BTW, if the Monday ELPA package is bad you can always trigger another
release to ELPA manually and don't need to wait for next Monday to have
cron run the release script.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2016-11-01 17:34 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
2016-11-01 17:33 ` Achim Gratz [this message]
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=87r36v85r0.fsf@Rainer.invalid \
--to=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
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).