emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Losing trust in Org: stable org-mode releases and unit tests for basic functionality
Date: Sun, 17 Jan 2016 11:30:09 +0100	[thread overview]
Message-ID: <87vb6s8pn2.fsf@Rainer.invalid> (raw)
In-Reply-To: 2016-01-17T10-45-36@devnull.Karl-Voit.at

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

That's the development branch which can introduce new features and
remove old ones at any time, you should be on maint if you want
"stable".  If you want even more stable, then don't update unless you
hit a bug that is fixed in maint.

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

There already is, it's called "maint".  And if any tests fail on your
machine, then the convenience target "up2" doesn't install the resulting
Org, so you never see that broken version.

> 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?

No, but I'd say you shouldn't use the development version of Org and you
shouldn't run Org directly from the Git worktree.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2016-01-17 10:30 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 ` Losing trust in Org: stable org-mode releases and unit tests for basic functionality Karl Voit
2016-01-17 10:30   ` Achim Gratz [this message]
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=87vb6s8pn2.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).