From: Corwin Brust <corwin@bru.st>
To: emacsq <laszlomail@protonmail.com>
Cc: Po Lu <luangruo@yahoo.com>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Releasing small, not critical features as bugfixes
Date: Sun, 10 Apr 2022 13:31:50 -0500 [thread overview]
Message-ID: <CAJf-WoToVObUJwm8vJwHqfdGWm0sOEmYiWe5tVc5n5T_4M802Q@mail.gmail.com> (raw)
In-Reply-To: <DVdyZnJB2ym2hIuDAW0XASGrtY8md4BgxvXuzDfEdIswpgLgrBkDe_7JgZK8HKKVgWb_pr8xtJSlPV-mfMOoUrFe_t_uFcsDP7VG5WL0lUs=@protonmail.com>
On Sun, Apr 10, 2022 at 11:38 AM emacsq <laszlomail@protonmail.com> wrote:
>
> So practically this branch could be kept up to date automatically by a script, there would be no additional work for developers aside from optionally marking commits for this low risk branch if they think their changes can also go for early release.
>
If your goal is to convince Emacs developers that it would be a small
amount of effort to maintain a separate branch that is Release plus
"simple improvements and fixes from trunk", perhaps creating a "fork"
that introduces the proposed new branch could be a way to demonstrate
that it is "low risk" and "no additional work".
next prev parent reply other threads:[~2022-04-10 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 6:16 Releasing small, not critical features as bugfixes emacsq
2022-04-10 11:45 ` Po Lu
2022-04-10 16:37 ` emacsq
2022-04-10 18:31 ` Corwin Brust [this message]
2022-04-10 20:00 ` emacsq
2022-04-11 3:20 ` Po Lu
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJf-WoToVObUJwm8vJwHqfdGWm0sOEmYiWe5tVc5n5T_4M802Q@mail.gmail.com \
--to=corwin@bru.st \
--cc=emacs-devel@gnu.org \
--cc=laszlomail@protonmail.com \
--cc=luangruo@yahoo.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.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).