emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-bbdb-anniversaries, bbdb v3
Date: Tue, 08 Mar 2016 11:35:27 -0500	[thread overview]
Message-ID: <87lh5t3p2o.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: rq93rcxso9.ln2@news.c0t0d0s0.de

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> Nick Dokos <ndokos@gmail.com> writes:
>
>> Michael Welle <mwe012008@gmx.net> writes:
>>
>>>>> I use Org 8.3.4 from the repository. There is no o-b-a-f in it, just the
>>>>> regular org-bbdb-anniversaries.
>>>>
>>>> That's strange: I just updated to 8.3.4 and o-b-a-f is present.
>>> indeed:
>>>
>>> ~/.emacs.d/elpa/org-plus-contrib-20160307> grep -ri
>>> org-bbdb-anniversaries-future *
>>> ~/.emacs.d/elpa/org-plus-contrib-20160307> 
>>>
>>> Is that a function in org-bbdb.el?
>>>
>>
>> Yes:
>>
>> ,----
>> | org-bbdb-anniversaries-future is an autoloaded compiled Lisp function
>> | in ‘../org-mode/lisp/org-bbdb.el’.
>> | 
>> | (org-bbdb-anniversaries-future &optional N)
>> | 
>> | Return list of anniversaries for today and the next n-1 days (default n=7).
>> `----
>>
>> I don't use ELPA so I may be completely wrong, but I thought ELPA
>> packages the maint branch, not the master branch. I think o-b-a-f
>> only exists in master, so it will appear in org-9.x
> ah, that was my question in my other post. I found your change set in
> master, but wasn't unsure on which branch the packages are based.
>
> Now I have to make my mind up, if I just wait or if I pull the master
> branch ;). 
>

I don't think o-b-a-f by itself is sufficient reason to upgrade :-)

I'm not going to say anything new or profound here, but it's worth
reiterating:

- if you depend on current org for "production" (with deadlines and
  deliverables that cannot be compromised), then you should probably
  leave your work machine alone. If you want to test, you should probably
  install master on a different machine (if you don't have a different
  physical machine, a VM will do fine) and test carefully before
  upgrading your work machine.

- if you can afford some breakage in your workflows and can either debug
  the failures or provide detailed information (backtraces, profiles
  etc) about them, I think the devs would appreciate that, but any
  testing you can do is probably worthwhile.

- That said, I think master is very stable, but there are backward
  incompatibilities in various places (check ORG-NEWS for details
  and the mailing list for breakage reports to see if they would affect
  you). The sooner you start getting ready, the smoother the transition
  will be.

--
Nick

  parent reply	other threads:[~2016-03-08 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ipa2rcx5nc.ln2@news.c0t0d0s0.de>
2016-03-08  9:25 ` org-bbdb-anniversaries, bbdb v3 Marco Wahl
     [not found]   ` <7hp2rcx89n.ln2@news.c0t0d0s0.de>
2016-03-08 13:08     ` Nick Dokos
2016-03-08 15:43       ` org-bbdb-anniversaries-future Georges
     [not found]       ` <md83rcxlt8.ln2@news.c0t0d0s0.de>
2016-03-08 15:50         ` org-bbdb-anniversaries, bbdb v3 Nick Dokos
     [not found]           ` <rq93rcxso9.ln2@news.c0t0d0s0.de>
2016-03-08 16:35             ` Nick Dokos [this message]
     [not found] ` <4cc3rcxgpb.ln2@news.c0t0d0s0.de>
2016-03-08 16:59   ` Nick Dokos

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=87lh5t3p2o.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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/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).