emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Phillip Lord <phillip.lord@russet.org.uk>,
	Michael Alan Dorman <mdorman@jaunder.io>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: stable org-plus-contrib
Date: Thu, 11 May 2017 13:00:18 +0000	[thread overview]
Message-ID: <CAFyQvY3R3RRCOTr=Tb8RyYnUB9ioOLbRKLWx3RRgwagUGVjKmA@mail.gmail.com> (raw)
In-Reply-To: <87ziejlh6p.fsf@russet.org.uk>

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

On Thu, May 11, 2017, 8:20 AM Phillip Lord <phillip.lord@russet.org.uk>
wrote:

>
> Really? That's rather confusing. So, it means that a bug here is a bug
> in a release version?
>

Well, a bug's not a bug till it is seen :)

What is the buggy behavior that you find in the Elpa version?

Simply put, the Melpa version has the latest weekly cut from the maint
branch (minus the contrib packages), the org Elpa version is the same but
with contrib packages. So those are stable versions. If one finds a bug in
those, then they get fixed when reported.

New big features get added to the master (devel) branch.

That said, I have been using the master branch as my daily driver for over
a year. As of now I don't see any bug that affects my workflow.

> --

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1367 bytes --]

  reply	other threads:[~2017-05-11 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 21:06 stable org-plus-contrib Phillip Lord
2017-05-10 21:23 ` Michael Alan Dorman
2017-05-11 12:19   ` Phillip Lord
2017-05-11 13:00     ` Kaushal Modi [this message]
     [not found]       ` <WM!95bbd6ceb481aab8cbf3d9262552b21760c689d7c35d9f4edb8a929f7d2fab7d73a59723c5b82ea98c7e402a4dc4e7e6!@mailhub-mx5.ncl.ac.uk>
2017-05-11 13:20         ` Phillip Lord
2017-05-11 13:50           ` Kaushal Modi
2017-05-14  7:44             ` Michael Welle

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='CAFyQvY3R3RRCOTr=Tb8RyYnUB9ioOLbRKLWx3RRgwagUGVjKmA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdorman@jaunder.io \
    --cc=phillip.lord@russet.org.uk \
    /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).