unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE
@ 2015-02-21 12:45 Eric Abrahamsen
  2015-02-21 20:57 ` Glenn Morris
  0 siblings, 1 reply; 3+ messages in thread
From: Eric Abrahamsen @ 2015-02-21 12:45 UTC (permalink / raw)
  To: 19913


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.





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE
  2015-02-21 12:45 bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE Eric Abrahamsen
@ 2015-02-21 20:57 ` Glenn Morris
  2015-02-22  1:10   ` Eric Abrahamsen
  0 siblings, 1 reply; 3+ messages in thread
From: Glenn Morris @ 2015-02-21 20:57 UTC (permalink / raw)
  To: Eric Abrahamsen; +Cc: 19913


I think you're making this more complicated than it is.
Code for Emacs itself should be compatible with the trunk.
Anything else is pointless.
Code for elpa.gnu.org should be compatible with the latest Emacs release.
If you want to support older releases, fine, but IMO a waste of time.





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE
  2015-02-21 20:57 ` Glenn Morris
@ 2015-02-22  1:10   ` Eric Abrahamsen
  0 siblings, 0 replies; 3+ messages in thread
From: Eric Abrahamsen @ 2015-02-22  1:10 UTC (permalink / raw)
  To: Glenn Morris

Glenn Morris <rgm@gnu.org> writes:

> I think you're making this more complicated than it is.
> Code for Emacs itself should be compatible with the trunk.
> Anything else is pointless.
> Code for elpa.gnu.org should be compatible with the latest Emacs release.
> If you want to support older releases, fine, but IMO a waste of time.

I'm certainly not saying this *should* be the convention, I thought it
already *was*, based on the automatic builds. If that's not the case, then
there's no need to do anything, and this bug should be closed.





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-02-22  1:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-21 12:45 bug#19913: 25.0.50; Add target version(s) information to etc/CONTRIBUTE Eric Abrahamsen
2015-02-21 20:57 ` Glenn Morris
2015-02-22  1:10   ` Eric Abrahamsen

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).