From: Bastien <bzg@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Release 9.3.8
Date: Mon, 07 Sep 2020 19:45:04 +0200 [thread overview]
Message-ID: <878sdlscpr.fsf@gnu.org> (raw)
In-Reply-To: <87blih33i8.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Mon, 07 Sep 2020 19:23:11 +0200")
Hi Kévin,
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> - Once 9.4 is released, will the maint branch be updated to this
> version?
Yes. See https://orgmode.org/worg/org-maintainance.html
> - 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.)
Yes, thanks.
> - 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.
... because 9.4 is not yet released - or am I missing something?
> 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?
On what commit would I add the "release_x.(y+1)-rc" on master, since
master is always moving forward?
I would like to keep things simple here: let's have annotated tags for
releases and... master.
Let me know if I miss a very obvious use-case for a better setup.
--
Bastien
next prev parent reply other threads:[~2020-09-07 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:49 Release 9.3.8 Bastien
2020-09-07 17:23 ` Kévin Le Gouguec
2020-09-07 17:45 ` Bastien [this message]
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 \
--in-reply-to=878sdlscpr.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kevin.legouguec@gmail.com \
/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).