From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 19913@debbugs.gnu.org
Subject: bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE
Date: Sat, 21 Feb 2015 20:45:21 +0800 [thread overview]
Message-ID: <874mqf77ry.fsf@ericabrahamsen.net> (raw)
A bit of information that should be in etc/CONTRIBUTE, but isn't:
When contributing patches to Emacs proper, which versions should be
targeted? How should one get them as "compile-clean" as possible? At the
moment randomsample.de seems to be down, but I recall that the code is
automatically built against 24.1, 24.2, HEAD, and a couple of XEmacs
flavors. I also recall having a hard time finding git branches that
corresponded exactly to the buildbot versions. I'm also so far totally
unable to build XEmacs at all, but that's a separate problem.
So, under the "Supplemental information for Emacs Developers" heading, I
propose another heading that goes something like this:
** Backwards Compatibility
New Emacs code should be compatible with the following older versions:
- [LIST OLDER VERSIONS HERE]
Git branches tracking the above Emacs versions are in the official Git
repository, with branch names that look like "back_compat/*" [NOT TRUE,
I'M MAKING THIS UP, BUT I THINK IT'S A GOOD IDEA. WHERE DO THE
BUILDBOT'S TEST VERSIONS COME FROM, ANYWAY?]. XEmacs can be
obtained from http://www.xemacs.org/.
For larger patches, please take the time to apply your patch to these
different versions, and ensure that Emacs builds without error.
Note that the Emacs codebase is automatically built every X DAYS,
against each of the above-mentioned versions. Should any patch you
contribute cause an error in one of these version builds, you'll receive
an automatic notification email from the buildbot.
Anyway, I think something like that would be helpful.
next reply other threads:[~2015-02-21 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 12:45 Eric Abrahamsen [this message]
2015-02-21 20:57 ` bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE Glenn Morris
2015-02-22 1:10 ` Eric Abrahamsen
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=874mqf77ry.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=19913@debbugs.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.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).