From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: cannot update to latest beta
Date: Thu, 22 Sep 2016 22:01:53 +0200 [thread overview]
Message-ID: <D95FE67F-335E-405A-B66B-C598A2D34F30@elvenkind.com> (raw)
In-Reply-To: <720d0e44-5b99-a64d-907b-cdbb46e5d9d2@gmx.es>
Hi Pablo,
> Op 22 sep. 2016 om 20:53 heeft Pablo Rodriguez <oinos@gmx.es> het volgende geschreven:
>
>> On 09/21/2016 11:26 PM, Philipp Gesang wrote:
>> ···<date: 2016-09-21, Wednesday>···<from: Pablo Rodriguez>···
>>
>>> Dear list,
>>>
>>> although latest beta seems to be from 2016.09.20 21:12, I get updated to
>>> beta from 2016.09.12 18:27 when I run:
>>
>> The official download still has the 2016.09.12 timestamp:
>> http://pragma-ade.nl/download-2.htm How did you get that other
>> date? I hope the git mirror isn’t scraping the wrong page ;)
>
> Philipp,
>
> I know that there is a new beta reading the metadata from
> http://www.pragma-ade.com/general/qrcs/setup-en.pdf.
>
> Here is the revealing field:
>
> Creator: ConTeXt - 2016.09.22 10:48
True, this means there exists a new version of context somewhere. But what you do not know is that there is a third context release state. Besides 'current' and 'beta' there is also 'latest'.
'Latest' contains experimental and/or in development code that needs to be shared for further testing or development. The easiest way for Hans to do that is to upload a new version to the website, and whenever any version of context is uploaded, the qrcs are uploaded as well.
An easier and safer way to check for a new context release is to browse through the 'download' section of the Pragma website, which is always auto-updated in the release process. Or just run first-setup whenever you feel like it ;)
Best wishes,
Taco
>
> When a new beta is realeased, this is the easiest way for me to know.
>
> But probably Hans is busy with the ConTeXt Meeting next week and he
> didn’t upload the beta.
>
> Many thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-09-22 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 16:21 Pablo Rodriguez
2016-09-21 21:26 ` Philipp Gesang
2016-09-22 18:53 ` Pablo Rodriguez
2016-09-22 20:01 ` Taco Hoekwater [this message]
2016-10-11 16:36 ` Mohammad Hossein Bateni
2016-10-12 18:36 ` Philipp Gesang
2016-10-12 19:21 ` Aditya Mahajan
2016-10-13 19:42 ` Philipp Gesang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D95FE67F-335E-405A-B66B-C598A2D34F30@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).