Re: RFC: creating a bison-announce list
Simon Richter <[email protected]>
| Newsgroups | gmane.comp.parsers.bison.general |
|---|---|
| Message-ID | <[email protected]> |
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 if Bison users were given a chance to try a beta before the final release, or even if Bison users were warned about a new release earlier. I think the problem is that most users use bison through the distributions and are just updating when new packages turn up. For Debian, there'd be the option of making pre-releases available as "experimental" packages that the package manager will not select automatically unless being explicitly instructed to. Not sure how other distributions handle this. Ideally, what we'd want is for users to test new Bison versions before a new release is tagged, and give feedback early on. 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 would have to be on board. I'd possibly be interested in prerelease tags in git that match a certain regex (/*rc*/ would probably work), so I can have Jenkins monitor that, that is more useful to me than a mail. I'm not sure there are many people left who build Bison from source packages and use it themselves -- those would be the target audience of the announce mailing list. On the other hand, if there is a prerelease tag, writing a mail about that might still be useful to someone. What would also be possible would be a CI system that test-compiles a number of prominent open source projects with HEAD Bison and feature branches before merging, but that would also require volunteers to actually do this. On the upside, these don't need to be distribution package maintainers, and it might even be feasible to do this as a (somewhat boring) GSoC project. Simon _______________________________________________ [email protected] https://lists.gnu.org/mailman/listinfo/help-bison
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEtjuqOJSXmNjSiX3Tfr04e7CZCBEFAlwkRxMACgkQfr04e7CZ CBGnnwgAr40TkScgjx6DwLeavVv3OLTnXjZSGaw2rZFKI8XaxLTvqBKe0I403cIF WEQlTX9NNwwBZyej8iwyeg1ZfcCUanIZT34cZf2/eSmR36W/6HnU0oLJnzBUb1no 5OufWVgUbHrdJZiO+zEKxd4aLUpZ2vd2tyRsLR44793do0xEoB1pIqf702bbT5Z+ RD30BTWvwAU94ix92cCtFPjj8MP1Vhz83pVBEI2vAmlVe4vIVnG3wwBbhjvefZOy NUwU2amJacS++q1AqkH2PtW+uGG1chKQsqJs/YF8RxeWUZYtEuvWh9/KJHl8FgIb HMEGlpMrM0kfKvQWNm9ulW97VcVzEw== =Zu0N -----END PGP SIGNATURE-----