Hi Akim,
On 06.01.19 09:10, Akim Demaille wrote:
> It has been asked to explicitly mark releases on git, so that CIs can trigger
> builds automatically with these releases. This is already the case: tags
> mark releases (betas and stable).
Will it be sufficient to test betas with existing pro
> Le 24 déc. 2018 à 18:00, Akim Demaille a écrit :
>
> Hi all,
> [...]
> Maybe creating bison-announce, which would be only about major events
> (releases and prereleases), would help?
I have created bison-annou...@gnu.org. To subscribe to it, two options:
- https://lists.gnu.org/mailman/li
Hi Simon,
> On 27 Dec 2018, at 04:29, Simon Richter wrote:
>
> [...]
>
> [...] Setting up a CI
> system that pulls "experimental" Bison into a chroot and test-compiles a
> project there is doable with medium effort, but we'd have to actively
> convince people to do that, and package maintainers
Hi,
On 24.12.18 18:00, Akim Demaille wrote:
> Recent history has shown that bugs are discovered too late, in a rather
> incremental fashion (I'm about to release 3.2.4), mostly revealed when Bison
> is finally updated in the main distros. I believe that much of this could
> have been avoided
Hi all,
Recent history has shown that bugs are discovered too late, in a rather
incremental fashion (I'm about to release 3.2.4), mostly revealed when Bison is
finally updated in the main distros. I believe that much of this could have
been avoided if Bison users were given a chance to try a b
