From: "Kévin Le Gouguec" <email@example.com> To: firstname.lastname@example.org Subject: Re: Release 9.3.8 Date: Mon, 07 Sep 2020 19:23:11 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Bastien <email@example.com> writes: > Hi all, > > I'm releasing Org 9.3.8, a bugfix release. > > Enjoy! Thanks for this release 🎉 > The next release will be 9.4: if you have outstanding important bugs > you would like to point to or to report, please go ahead. No bug to report, however I've got a couple of questions wrt. versions: - Once 9.4 is released, will the maint branch be updated to this version? - Will Emacs's maintenance branch (emacs-27) be updated with Org 9.3.8, so that Emacs 27.2 includes all bugfixes for 9.3? (If so, I can open a new report on Debbugs to track this, as suggested by Stefan K.) - During the development of 9.4, AFAICT, while the "Version:" comment in org.el sayd "9.4-dev", the org-version variable matched the latest tag, i.e. 9.3.x. I therefore couldn't figure out a way to check for 9.4 programmatically. Would it make sense to: - set a "release_x.(y+1)-rc" tag on master once version "x.y" is released and goes in the maint branch, - in targets.mk, when computing ORGVERSION, add "--first-parent" to "git describe", so that org-version matches this rc-tag when compiling Org's master branch? At any rate, thanks for all the work.
next prev parent reply other threads:[~2020-09-07 17:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-07 15:49 Bastien 2020-09-07 17:23 ` Kévin Le Gouguec [this message] 2020-09-07 17:45 ` Bastien 2020-09-08 5:35 ` Kévin Le Gouguec 2020-09-09 8:17 ` Bastien 2020-09-10 0:45 ` Kyle Meyer 2020-09-10 6:32 ` Check for master branch from Elisp (was: Release 9.3.8) Kévin Le Gouguec
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Release 9.3.8' \ /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 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).