Re: [O] Versioning of worg content

[Achim Gratz]

Bastien writes:
> No.  Worg needs love.  And yes, we could tag Worg's repository
> with Org-mode versions, the same as we would do with documentation.

If you are talking about the Git repository behind Worg, then:

a) Yes, we could give that repository version tags.
b) No, we shouldn't do that unless SomeOne™ keeps all of Worg consistent
with the Org releases.

If you are saying instead that the examples in Worg should be annotated
with the Org version that they were provided for (or last tested to be
working at), that would be good, but see b) above.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: [O] Versioning of worg content

[Bastien]

Hi Stefan,

"Stefan-W. Hahn"  writes:

> is their a defined proceeding of how to cope with incompatible changes of
> org-mode in the examples at orgmode.org/worg?

No.  Worg needs love.  And yes, we could tag Worg's repository
with Org-mode versions, the same as we would do with documentation.

-- 
 Bastien

[O] Versioning of worg content

[Stefan-W. Hahn]

Hello,

is their a defined proceeding of how to cope with incompatible changes of
org-mode in the examples at orgmode.org/worg?

Just stumbled about examples for org-agenda where org-agenda-ndays is still
used when I already using org 9.1 where the alias is removed.

With kind regards
Stefan

-- 
Stefan-W. Hahn  It is easy to make things.
It is hard to make things simple.