Re: release process analysis

2020-09-29 Thread Bruno Haible
Jeffrey Walton wrote: > I think the next improvement to the release process should engineer > around human behavior. Here, the human behavior is, most folks avoid > pre-release testing, and then jump right to the release. > ... > It has been my experience that once you perform the minor version > r

Re: release process analysis

2020-09-29 Thread Dagobert Michelsen
Hi Paul, Am 29.09.2020 um 22:56 schrieb Paul Eggert : > On 9/29/20 12:00 AM, Dagobert Michelsen wrote: >> This is not correct: there is continous integration on Solaris >> for quite some time now > > Yes, and I used that with this patch. Unfortunately the failure mode occurs > only when libsigse

Re: release process analysis

2020-09-29 Thread Jeffrey Walton
On Mon, Sep 28, 2020 at 10:28 PM Bruno Haible wrote: > > It's a pity that grep-2.5 was released with such a mistake. > ... > How can we avoid such things? Just my 2-cents, but I think the technical controls are good. You have a CI pipeline, and you are testing on multiple platforms. You are also

Re: release process analysis

2020-09-29 Thread Paul Eggert
On 9/29/20 12:00 AM, Dagobert Michelsen wrote: This is not correct: there is continous integration on Solaris for quite some time now Yes, and I used that with this patch. Unfortunately the failure mode occurs only when libsigsegv is installed 3rd-party on Solaris, which was not the situation

Re: release process analysis

2020-09-29 Thread Dagobert Michelsen
Hi Bruno, Am 29.09.2020 um 04:28 schrieb Bruno Haible : >- we don't have continuous integration on Solaris, This is not correct: there is continous integration on Solaris for quite some time now and status changes are reported automatically to grep-de...@gnu.org as well: https://buildfarm.o