On Thu, Nov 19, 2015 at 8:12 PM, Hans Hagen <pragma@wxs.nl> wrote:

On 11/19/2015 8:09 PM, Mojca Miklavec wrote:

On 19 November 2015 at 19:12, Alan BRASLAU wrote:

Hi,

I built and committed binaries for linux and freebsd, 64bit and 32bit.

It looks like the sources contained r5551 when you synced, so
according to Luigi you will most likely need to repeat the process :(

The mac binaries are being compiled right now thanks to Hans.

i uploaded the beta that is needed for these binaries

-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------

$ luatex --version

This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) (rev 5550)

rev 5550 is hardcoded, ie it doesn't strictly depends on the current rev. of beta.

Given that the only source for beta is

tags/beta-0.85.0

in the end this "(rev 5550)" is "just a number".

When we will announce the beta, the code will be frozen in the svn, and of course it is

associated with a revision number too, which usually is greater.

So, to keep the things simple, we fix the rev. to that one of the trunk and we tolerate a bit of delta.

The most important things in the banner are

"/dev", which means not from a stable TeXLive

and "(rev. 5550)" which means that it's a beta, ie frozen.

For example, for trunk we have

$ luatex --version

This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev)

and for TEXLive 2015

# luatex --version

This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238)

i.e. "stable TL, code from beta frozen"

which is the what we tend to do.

If there is a patch to commit after the announcement,

then we will make 0.85.0.1 (or 0.85.1, it depends if we also add something new o rewrite something)

because as I hev said, after an announcement the code of a beta is frozen.

luigi