emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Losing trust in Org: stable org-mode releases and unit tests for basic functionality
Date: Sun, 17 Jan 2016 11:12:19 +0100	[thread overview]
Message-ID: <2016-01-17T10-45-36@devnull.Karl-Voit.at> (raw)
In-Reply-To: 55CA2E6B.4060102@gmail.com

Hi!

I want to re-heat the discussion of last summer about stable
releases[1] of Org-mode:

* Scott Randby <srandby@gmail.com> wrote:
> While I've used Org's development version in the past, I stopped doing 
> that due to my failure to learn how to use git (no time) and other 
> issues. Now, I only use the stable releases. But the latest 8.3 release 
> doesn't seem so stable to me[...]

For Scott (I think) and for me "stable" means: save to use with my
current data without corrupting things or losing features of my
workflows.

I had several occasions where "git pull origin master" ended up in
much work for fixing my large set of Org-mode data. 

For example several times, org-todo -> DONE on recurring tasks lead
to DONE and closed tasks.

This is quite evil behavior because I rely heavily on a reliable Org
for currently 1162 open tasks in several dozen files. When such a
bug finds its way to my system and I don't recognize it (which is
highly likely in this case), I lose important tasks and even worse:
I lose my trust in Org-mode.

The most current issue of "recurring tasks get closed"[2] is fixed
(with another scoping issue newly introduced[3]): please don't
discuss this issue or any other concrete bug/issue in this thread.

It's just an example to make my point clear:

What I am trying to raise is a discussion on whether or not there
should be a stable git branch or at east some kind of unit test set
that make sure that really basic functionality doesn't get broken
without being recognized instantly. In my humble opinion, there has
to be some kind of continuous integration tests where breaking
things rings loud whistles.

Unfortunately, I don't have time to follow all the interesting
discussions on the mailing list any more. Does this imply, I can't
use Org-mode any more?

The only alternative I can think of is using the conservative(?)
Org-mode which comes with Emacs from my current Linux distribution.
However, I remember multiple cases where those Org-mode versions
still had some bugs and the recommended solution was "upgrade to
Org-mode git commit abcdef". This is how I started with Org-mode
from git in the first place!

So: what should I do to get reliable Org-mode in future to minimize
the chances of losing tasks or my trust in Org?

[1] http://thread.gmane.org/gmane.emacs.orgmode/99881/
[2] http://thread.gmane.org/gmane.emacs.orgmode/104219
[3] http://thread.gmane.org/gmane.emacs.orgmode/104219/focus=104260

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

  parent reply	other threads:[~2016-01-17 10:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 17:18 Stable releases Scott Randby
2015-08-11 18:33 ` Ista Zahn
2015-08-11 19:34   ` Suvayu Ali
2015-08-11 20:56 ` Rasmus
2015-08-12 16:14   ` Scott Randby
2015-08-12 13:39 ` Nicolas Goaziou
2015-08-12 14:38   ` Peter Salazar
2015-08-12 15:57   ` Scott Randby
2015-08-12 22:56     ` Rasmus
2015-08-18 16:44   ` Bastien
2015-08-18 17:30     ` Bastien
2015-08-12 17:37 ` Achim Gratz
2015-08-12 19:06   ` Scott Randby
2015-08-13  9:32     ` Eric S Fraga
2015-08-13 13:28       ` Scott Randby
2015-08-18 17:36 ` Bastien
2015-08-18 17:52   ` Scott Randby
2015-08-18 20:40   ` Russell Adams
2015-08-18 22:26     ` Bastien
2015-08-19 20:00     ` Rasmus
2015-08-20 23:03       ` Bastien
2015-08-20 23:56         ` Thomas S. Dye
2015-08-21  7:21           ` Suvayu Ali
2015-08-22 17:32             ` Thomas S. Dye
2015-08-22 17:44               ` Achim Gratz
2015-08-22 17:55                 ` Thomas S. Dye
2015-08-22 18:00                   ` Achim Gratz
2015-08-22 18:23                     ` Thomas S. Dye
2015-08-22 18:53                       ` Thomas S. Dye
2015-08-22 18:57                         ` Achim Gratz
2015-08-22 19:06                           ` Thomas S. Dye
2015-08-21 18:37         ` Rasmus
2015-08-19  8:51   ` Nicolas Goaziou
2015-08-19  9:36     ` Bastien
2015-08-19 14:51       ` Nicolas Goaziou
2015-08-19 19:57   ` Rasmus
2016-01-17 10:12 ` Karl Voit [this message]
2016-01-17 10:30   ` Losing trust in Org: stable org-mode releases and unit tests for basic functionality Achim Gratz
2016-01-18 13:47     ` Karl Voit
2016-01-17 13:41   ` Marco Wahl
2016-01-18 14:06     ` Karl Voit
2016-01-19  9:00       ` Marco Wahl

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=2016-01-17T10-45-36@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).