From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Upstream synchronization documentation Date: Mon, 03 Jul 2017 12:35:32 +0200 Message-ID: <87fuedyfij.fsf@gmx.us> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37335) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRyi0-0000sV-4Y for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 06:36:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dRyhw-00073F-3g for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 06:36:00 -0400 Received: from [195.159.176.226] (port=53794 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dRyhv-00072q-R5 for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 06:35:56 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dRyhk-0000ZM-4f for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 12:35:44 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Hi, The documentation in README_maintainer is a bit outdated wrt. synchronizing with upstream Emacs. I have updated the to best of my knowledge in the attached patch. I would be happy to push it, if there are no objections. It would also be great if someone would let me know about the mistakes that are undoubtedly in the draft. Rasmus -- I hear there's rumors on the, uh, Internets. . . --=-=-= Content-Type: text/x-diff Content-Disposition: inline; filename=0001-Update-README_maintainer-with-upstream-synchronizati.patch >From 2126076308e13efbacf115afc3856d2c1da541fa Mon Sep 17 00:00:00 2001 From: Rasmus Date: Mon, 3 Jul 2017 11:48:58 +0200 Subject: [PATCH] Update README_maintainer with upstream synchronization instructions * README_maintainer: Update with upstream synchronization instructions. --- README_maintainer | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 57 insertions(+), 4 deletions(-) diff --git a/README_maintainer b/README_maintainer index 6b162aa52..bf2678da3 100644 --- a/README_maintainer +++ b/README_maintainer @@ -88,9 +88,62 @@ Org and contributed libraries. org-latest* snapshots are built from the *master* branch. -* Synchronization with Emacs - -** Updating etc/ORG-NEWS +* Synchronization Org and upstream Emacs +Org should be kept in sync with the upstream [[http://git.savannah.gnu.org/cgit/emacs.git/tree/][Emacs repository]]. +Sometimes Org is changed in the Emacs upstream repo. These changes +should be backported. Likewise, new stable releases of Org should be +added to Emacs. +** Backporting changes from upstream Emacs +To check for backports from the Emacs upstream repository, one can use +the following =git= command, cutesy of [[http://permalink.gmane.org/gmane.emacs.devel/215861][Kyle Meyer]], + +: git log $rev..origin/emacs-25 -- lisp/org doc/misc/org.texi etc/refcards/orgcard.tex + +where =$rev= is the last commit from the =emacs-25= branch that was +backported. The same should be done for the =master= branch. + +One may also use this [[http://git.savannah.gnu.org/cgit/emacs.git/atom/lisp/org/][Atom feed]] to see upstream changes. +** Updating the Org version in upstream Emacs +After a new release of Org, it should be synced to the Emacs +repository. + +Typically, Org can be synchronized by copying over files from the +=emacs-sync= branch of the Org repository to the =master= branch of Emacs +repository. The =emacs-sync= branch has a few extra changes compared to +the =maint= branch. If the Emacs maintainers are planning a new release +of Emacs soon, it is possible that another branch, e.g. =emacs-25=, +should be used. + +If you are synchronizing a major release of Org, it may be useful to +use a separate branch before merging, e.g. =scratch/org-mode-merge=. +This can then later be merged with the =master= branch, when everything +has been tested. + +Please also see [[http://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE][CONTRIBUTE]] in the Emacs repository. +*** Where to files go +The following detail where files in Org repository are copied to in +the Emacs repository. +*** =org-mode/doc= +- =org.texi= :: Copy to =emacs/doc/misc=. It may be necessary to replace, + ~@include org-version.inc~ #+end_src with ~@set VERSION 9.0.9~ + or similar. +- =orgcard.tex= :: Copy to =emacs/doc/refcards=. Make sure that + ~\def\orgversionnumber~ and ~\def\versionyear~ are up + to date, if necessary. +- =library-of-babel.org= :: Copy to =emacs/etc/org=. +*** =org-mode/etc= +- =styles/*= :: Copy to =emacs/etc/org=. +- =schema/*.rnc= :: Copy to =emacs/etc/schema=. +- =schema/schemas.xml= :: New entries of this files should be added to + =emacs/etc/schema/schemas.xml=. +- =ORG-NEWS= :: Copy to =emacs/etc= +*** =org-mode/lisp= +- Copy =*.el= files to =emacs/lisp/org=, except =org-loaddefs.el=! +- You should create =org-version.el= in =emacs/lisp/org=. The file is + created when you =make= Org. +*** TODO =org-mode/testing= +** Outdated notes +*** Updating etc/ORG-NEWS Latest changes in Emacs are described in Emacs =etc/NEWS=, and latest changes in major Emacs packages are described in =etc/ORG-NEWS=. @@ -100,7 +153,7 @@ always should), you need to update Org's =etc/ORG-NEWS= file so that you can merge it with that of Emacs. There is one top-level section for each release that is merged with Emacs. -** Merging with Emacs trunk branch +*** Merging with Emacs trunk branch This is still a significant headache. Some hand work is needed here. -- 2.13.2 --=-=-=--