Re: about new releases

[Alex Light <allight@...>]

Honestly I think the issue is that this ABI breakage is exactly the kind of issue that's easy to slip by. It's not obvious even reading the old discussions of the bug resetthread is fixing that the fix is an ABI break and the description of the lua numbering scheme is 'Different releases of the same version ... are binary compatible (ABI compatible)'. I can see why nobody would have tried the sort of tests that could expose this.

In any event this is now a pretty major bug with 5.4.5 that needs to be addressed somehow. Possibly with a relatively rapid release of 5.4.6 that just fixes this bug by adding a new lua_resetthread2 and reverting the ABI break.

-Alex

On Tue, May 2, 2023 at 10:24 AM Viacheslav Usov <via.usov@gmail.com> wrote:

On Tue, May 2, 2023 at 3:38 PM Roberto Ierusalimschy
<roberto@inf.puc-rio.br> wrote:
>
> What is really sad is that people had 20 days to point out issues,
> and nothing. Then, hours after the freeze they come shouting at us,
> as if we had just announced something completely unexpected.

I have missed the entire thing, so I think it will be fair to say that
20 days is not sufficient notice, at least the way it is given
currently.

I'd think any release announcement should happen much earlier, even if
the release date is not certain, with subsequent updates of the
schedule once it becomes more realistic. I'd also publish the release
schedule and its updates at lua.org regardless of any posts in l-l.

Cheers,
V.